# fix\(mobile\): the first tab tap after folding the Duo reaches the app · pingdotgg/t3code

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

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

Visibility: public

Requested revision: ed4b4a844f190019cf49accc7564f8463d89edc5

Requested commit: ed4b4a844f190019cf49accc7564f8463d89edc5

Commit: ed4b4a844f190019cf49accc7564f8463d89edc5

Tree: ca2792d6c0424bfce5c0bcaaf20c6d5895185ef9

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
fix(mobile): the first tab tap after folding the Duo reaches the app

After a fold or unfold, UIKit delivers didSelectTab: about 150 ms after
shouldSelectTab:. The layout commits from the pose change land in that
window, and every Screens container update cleared the flag that marked
the selection as the user's. Screens then dropped it as programmatic, so
the native tab changed but onTabSelected never fired and the app kept
the old tab's state until a second tap.

Screens 5.0.0-t3.31 takes upstream's fix (software-mansion/react-native-screens#4862
and #4890): the tab controller marks its own selectedTab writes, which
UIKit reports synchronously, and treats every other didSelectTab: as a
user selection. The release also carries the opt-in horizontal sheet
bars from pingdotgg/react-native-screens#2, unused until the sheets
change adopts them.

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

```

## Parents

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

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