Repository navigation
[Bug]: iPad only: drafts can't be opened or sent; long-press only offers Discard #13943
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Area
apps/mobile
Steps to reproduce
- On the T3 Code iPad app (1.3.0), type a prompt in a thread and leave it unsent, so it shows under Unsent in the sidebar with the Draft badge.
- Tap the draft row.
- Long-press the draft row.
Expected behavior
Tapping a draft opens it in the composer so it can be edited and sent. Long-press offers at least an Open/Send action alongside Discard.
Actual behavior
- Tapping the draft does nothing; it cannot be selected or opened.
- Long-press shows a context menu with only Discard.
- The only way to act on a draft is to delete it, so the draft cannot be sent.
Impact
Major degradation or frequent failure
Version or commit
T3 Code iPad app 1.3.0
Environment
iPadOS, T3 Code mobile app 1.3.0
iPad only. On iPhone (same app version) tapping a draft works: it opens the modal with the draft, ready to send.
Screenshots, recordings, or supporting files
Screenshot: long-press on a draft under "Unsent" shows only "Discard".
Workaround
None in the iPad app. Send the draft from the iPhone app or another client.
Regression
Worked in earlier versions: drafts could be opened and sent from the sidebar.
Activity
[-][Bug]: iPad app drafts can't be opened or sent; long-press only offers Discard[/-][+][Bug]: iPad only: drafts can't be opened or sent; long-press only offers Discard[/+]juliusmarminge commentedon Sep 27, 2026
Triage
Confirmed on
main(a727d1d976). Still present. Checked from source only; this was not re-run on an iPad.Tapping an Unsent draft is a no-op only in the iOS split sidebar. The iPhone path is fine, and the Discard-only long-press menu is the menu that ships on both.
The split sidebar (window at least 720×600, so a normal iPad, not an iPhone) is not in the root navigation tree.
SidebarNavigationShellwraps that column inNavigationIndependentTreewith a single route,SidebarThreads. The comment there says the stack is navigation-inert and that real navigation goes through callbacks created inAdaptiveWorkspaceLayout. Thread selection and “new thread on this branch” do that. Opening a draft does not.ThreadNavigationSidebarcallsusePendingTaskListActions()inside that isolated tree.openPendingTaskthen doesnavigation.navigate("NewTaskSheet", { screen: "NewTaskDraft", ... }). That navigator has noNewTaskSheetscreen and no parent to bubble to, so the action is dropped. The same handler covers “Sends on reconnect” rows, so those cannot be opened from the iPad sidebar either.On iPhone,
HomeRouteScreencalls the same hook from the root stack, which does ownNewTaskSheet. That is why the same 1.3.0 build opens the draft there. Android split view skipsSidebarNavigationShell, so this isolation is iOS-only.Long-press is working as written.
DRAFT_TASK_MENU_ACTIONSis only Discard, on phone and iPad. Discard still runs because it clears local draft state and never navigates. An Open item in that menu would hit the same deadnavigateuntil the tap path is fixed.This is not a recent 1.3.0 regression of a previously working iPad tap. The independent sidebar tree landed in #3514, and the pending-row handler was wired with
useNavigationinside it in #3670. Draft rows (#10260) reuse that handler. A window narrow enough to leave split view (under 720×600) uses the compact home list and should open the draft.Fix is to mint
openPendingTasknext tohandleNewThreadOnBranchinAdaptiveWorkspaceLayoutand pass it into the sidebar.confirmDeletePendingTaskcan stay where it is.