# fix\(mobile\): Back from a folded Duo thread returns to the thread list · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/commit/f9a3b5c2fbbf856382a26f81909690eb49c9e284)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

Requested revision: f9a3b5c2fbbf856382a26f81909690eb49c9e284

Requested commit: f9a3b5c2fbbf856382a26f81909690eb49c9e284

Commit: f9a3b5c2fbbf856382a26f81909690eb49c9e284

Tree: 06723013201701ccc9bd5a2949e960d51fec50f9

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
fix(mobile): Back from a folded Duo thread returns to the thread list

On a collapsed split (Duo folded, or a compact iPad window), UIKit nests
the detail column's navigation controller inside the list's. Back from the
first detail pops that nested controller as a whole, so no Split screen
leaves its own stack and react-native-screens never reports a dismissal.
The router kept Home + Thread while the list was on screen, and the
compact-column ref still read "secondary". The next row tap then renamed
the hidden route or pushed under it without showing the detail column.

The workspace columns now follow UIKit's appearance callbacks while
collapsed. When the list appears after the router's active detail began
leaving, the router pops those details from their source, which keeps any
presentation opened during the animation. Cancelled swipes and re-shown
details clear the pending pop. The visible column comes from those
callbacks and from collapse events instead of the last command sent, so
show() fires whenever the router and UIKit disagree.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

```

## Parents

- [aaa7380015abcf64411a887d28a596b52367001c](https://git.cafe/pingdotgg/t3code/commit/aaa7380015abcf64411a887d28a596b52367001c?format=markdown)

[Source at this commit](https://git.cafe/pingdotgg/t3code/tree/f9a3b5c2fbbf856382a26f81909690eb49c9e284?format=markdown)