-
-
Notifications
You must be signed in to change notification settings - Fork 492
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Encountering a white screen when navigating with latest alpha #208
Comments
Having the same issue, any thoughts? |
Could be related to #187? Are your screens nested in a stack inside a tab navigator? |
Same here. My screens are in stackNavigator inside of switchNavigator. I encounter white screens and strange glitching when navigating between stacks. Tested only on iOS simulator. |
I think being nested in another navigator was the problem -- it appears to work well after this PR: Still seems like a bug with react-native-screens though? |
Just to share my experience, in case it helps to pinpoint the issue. This issue also happens if you have the following structure:
If you are on the |
It seems to be fixed in the latest alpha 8 version. I don't have any lags after update. But the performance is way worse than without the lib Update: I'm on the last |
This is still definitely not fixed. I've tried fixing this on my fork, but to no avail. P.S. I am using alpha version 4 in my production build. Version 8 even with the fix in this commit https://github.com/infinitered/ignite-bowser/pull/289/files doesn't work properly (tested only on iOS physical device). There is still spacing at the bottom of the screen. |
Having issue with this still. Any thoughts? |
Have you tried the latest alpha version? I had a similar issue that was fixed by upgrading from alpha 8 to alpha 11. I'm not sure why but my issue is gone both on Android and iOS. |
I'm on alpha 15 now and this blank issue is still there on Android. iOS works much better and rarely have this problem. |
I can say that @limaAniceto issue still happening only on Android, and I'm on alpha 16. If I use "useScreens()" method, it works but with somes bugs, the problem is with "enableScreens()" |
Hello, I'm using alpha 17 and RN 0.61.5 and still have this issue on iOS |
alpha 18 has same issue, also result is not changed with useScreens |
I've downgraded to react-native-screens@^1.0.0-alpha.23 as the documentation is saying and removed the enableScreens, and now it looks fine on my side. |
fixes #208 For stack overriding reactSetFrame for active does nothing because active is always NO, so there's no regression. But it fixes in other cases (like stack navigation - not native one).
Issue is still there on Android with alpha.22. |
Can you open a new issue with some repro? |
Experiencing this issue, at least on android.
Any known solutions? |
@Legi0n1138 Please try react-native-screens@2.1.0 and report back if that did not solve the problem |
@kmagiera |
I'm still experiencing this issue with |
Related issue: infinitered/ignite-bowser#285
Steps to reproduce:
If I remove the
enableScreens()
in theapp.tsx
, it no longer exhibits this behavior. Reloading the second screen also fixes the issue temporarily until I click back, after which it turns white on the home screen.Any idea what's going on here?
The text was updated successfully, but these errors were encountered: