You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Mobile: undo of Settle puts the thread at the top of the active rows, not back in its place #35572
🤖 Claude Fable 5.2 filing on behalf of Theo. Found during device and web checks of other pull requests on 2026-11-12. Not a regression from them: each item below was also seen on the previous nightly or on main before those changes.
Area
apps/mobile
Steps to reproduce
In the mobile thread list, take an active thread that is not the first active row.
Settle it.
Tap Undo on the notice.
Expected behavior
The thread returns to the place it had before the settle.
Actual behavior
The thread returns at the top of the active rows.
Undo of an unpin does restore the old pin place, so the two undos behave differently.
Impact
Minor. The list order changes after an action the user reverted.
Version or commit
main at e89c8ce014e, and still on main at a909ea423cb.
Environment
iPhone 17 Pro simulator, iOS 26.5, dev client.
Notes
Not root-caused. It may be the list sort (latest activity first) acting on the time of the undo. If that order is intended, close this.
Fixed by #33248, now on main: On mobile, settle an active thread below the first row and tap Undo: it now returns to its previous position because Undo restores its saved Active ordering timestamp and any manual order key.
Activity
juliusmarminge commentedon Nov 14, 2026
Fixed by #33248, now on main: On mobile, settle an active thread below the first row and tap Undo: it now returns to its previous position because Undo restores its saved Active ordering timestamp and any manual order key.