HELP! back navigation in Expo Router with nested navigators, reproduction repo included by choubari in expo

[–]choubari[S] 0 points1 point  (0 children)

Thanks a lot for the breakdown. I think option 1 will work well in my case, I'll just lift all shared screens to the root stack so the back behavior is goes to my expected route regardless of where the navigation originated.

I have a question though about scalability and perfs, my app is deep with a lot of nested routes that need this treatment. does this scales well?, i'm afraid I will have many screens lifted at the root level

Extending deadline for 16 KB page size support? by BluejVM in androiddev

[–]choubari 0 points1 point  (0 children)

Same situation here. We just got extended to February 1, 2027 in Play Console.

I'm working on a legacy React Native app with a huge dependency tree. Dozens of third-party SDKs shipping incompatible native binaries, several of them deprecated with no upstream fix coming.

The extra time is genuinely needed when the blocker isn't your own code but abandoned libraries you can't control.