Hirbod @hirbod.dev · 07/12/2024Careful with navigation.preload() on native-stack. Preloading triggers react-freeze and stops rendering of your whole app. You _need_ to navigate to the preloaded screen to „unfreeze“. This is definitely a bug. Also cc @kzzzf.bsky.social 4110
Krzysztof Magiera @kzzzf.bsky.social · 08/12/2024Noted 🫡 but I’d expect this time for real this isn’t bug in screens. It just uses freeze on screens that aren’t visible which is the case of preloaded ones. So I’d require this information to be provided by navigation which is perhaps not happening 240
Hirbod @hirbod.dev · 07/12/2024github.com/software-man...github.comnavigation.preload() with enableFreeze breaks app, stopping rendering · Issue #2557 · software-mansion/react-native-screensDescription React Navigation v7 introduces navigation.preload(). If you preload a screen without navigating to it, the entire app stops rendering because react-freeze is triggered, halting the rend... 030
Hirbod @hirbod.dev · 07/12/2024I found the bug randomly. I had preloaded onPressIn but aborted the actual navigation (moved finger away). All screens stopped rendering anything. After a bit of testing I finally figured what happened. 030