Skip to content
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

Closed
jamonholmgren opened this issue Oct 31, 2019 · 22 comments · Fixed by #252
Closed

Encountering a white screen when navigating with latest alpha #208

jamonholmgren opened this issue Oct 31, 2019 · 22 comments · Fixed by #252

Comments

@jamonholmgren
Copy link

Related issue: infinitered/ignite-bowser#285

Steps to reproduce:

  1. Run these commands:
npm i -g ignite-cli
ignite new MyApp -b bowser --no-detox
cd MyApp
react-native run-ios
  1. Run it
  2. Click the "Continue" button and observe:

If I remove the enableScreens() in the app.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?

@bwoodlt
Copy link

bwoodlt commented Oct 31, 2019

Having the same issue, any thoughts? react-native:0.61.2 and react-native-screens: 2.0.0-alpha.6

@AfrazHussain
Copy link

Could be related to #187? Are your screens nested in a stack inside a tab navigator?

@makarkotlov
Copy link

makarkotlov commented Oct 31, 2019

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. react-native:0.61.3 and react-native-screens: 2.0.0-alpha.7

@jamonholmgren
Copy link
Author

jamonholmgren commented Nov 5, 2019

I think being nested in another navigator was the problem -- it appears to work well after this PR:

infinitered/ignite-bowser#289

Still seems like a bug with react-native-screens though?

@limaAniceto
Copy link

limaAniceto commented Nov 7, 2019

Just to share my experience, in case it helps to pinpoint the issue.

This issue also happens if you have the following structure:

createAppContainer(AppNavigator)
const AppNavigator = createSwitchNavigator({
        Auth: AuthStack,
        App: TabNavigator
})
const TabNavigator = createStackNavigator({
   myTab: createBottomTabNavigator(
                {
                    Home: HomeStack,
                    Profile: ProfileStack,
                })
})
const HomeStack = createStackNavigator(
    {
        home: HomeScreen,
        Other: OtherScreen
   });

If you are on the HomeScreen and click on a button to navigate to OtherScreen you get the blank screen. If you just remove enableScreens, it works

@makarkotlov
Copy link

makarkotlov commented Nov 7, 2019

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 alpha.11. The lib crashes my app when I try to navigate to other stackNavigator inside of switchNavigator

@AfrazHussain
Copy link

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.

@bwoodlt
Copy link

bwoodlt commented Nov 14, 2019

Having issue with this still. Any thoughts?

@sofiageo
Copy link

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.

@bjjeong
Copy link

bjjeong commented Nov 15, 2019

Still getting this issue on alpha 11. Have been having to use alpha-4 as it's the last version that doesn't have this problem. I'm on react-native@0.61.3

RNS

@nphivu414
Copy link

I'm on alpha 15 now and this blank issue is still there on Android. iOS works much better and rarely have this problem.

@tboerc
Copy link

tboerc commented Dec 3, 2019

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()"

@dcosmin2003
Copy link

Hello, I'm using alpha 17 and RN 0.61.5 and still have this issue on iOS

@mistikk
Copy link

mistikk commented Dec 12, 2019

alpha 18 has same issue, also result is not changed with useScreens

@dcosmin2003
Copy link

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.

https://reactnavigation.org/docs/en/getting-started.html

osdnk added a commit that referenced this issue Dec 17, 2019
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).
@bitsmanent
Copy link

Issue is still there on Android with alpha.22.

@osdnk
Copy link
Contributor

osdnk commented Jan 7, 2020

Can you open a new issue with some repro?

@bitsmanent
Copy link

@osdnk Sure, see #270

@alex-trofimov
Copy link

Experiencing this issue, at least on android.

"react-native-screens": "^2.0.0-alpha.15",
"react-native": "^0.61.5",
"react-navigation": "4.2.2",
"react-navigation-drawer": "1.4.0",
"react-navigation-stack": "1.7.3",
"react-navigation-tabs": "1.2.0",

Any known solutions?

@kmagiera
Copy link
Member

@Legi0n1138 Please try react-native-screens@2.1.0 and report back if that did not solve the problem

@alex-trofimov
Copy link

@kmagiera react-native-screens@2.1.0 solved the issue. Thanks!

@clems36
Copy link

clems36 commented Aug 6, 2020

I'm still experiencing this issue with "react-native-screens": "~2.9.0", both on iOS and android.
useScreens gives the same result.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.