# fix\(mobile\): returning to a tab clears its old detail instead of crashing · pingdotgg/t3code

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

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

Visibility: public

Requested revision: 3f0e6219d0f4d6f3a98911a8f592600cd50a096a

Requested commit: 3f0e6219d0f4d6f3a98911a8f592600cd50a096a

Commit: 3f0e6219d0f4d6f3a98911a8f592600cd50a096a

Tree: 2f02ec33a04f0403cefa50201a41f9617653746d

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
fix(mobile): returning to a tab clears its old detail instead of crashing

A tab switch pops the workspace to its list, so the tab you return to
drops the detail it was showing. Its column attaches the empty
placeholder and removes the old screen in one commit, but Reanimated
held the removal for exiting animations inside the screen, because it
only exempts legacy Screens components. Screens pushed the placeholder
over the still-mounted pull request, then popped a screen that was no
longer on top: debug builds crashed with "Attempt to pop non-top
screen", and release builds would pop the placeholder and leave the
stale pull request showing. This affects iPad and iPhone Duo columns,
folded or not.

Reanimated now treats Screens v5 stack, split and tab screens like
legacy screens, so their removal lands in the same mount as the rest of
the commit.

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

```

## Parents

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

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