2.0.0-alpha.5 breaks my tabbed stackview

Hiya, I just updated from 2.0.0-alpha.4 to 2.0.0-alpha.5 and it breaks my current set up.

<BottomTabNavigator />
- <StackNavigator />
- <StackNavigator />
- <StackNavigator />
- ...

Switching the BottomTabBar main children works fine but after adding/opening a new StackView to open a deeper view it shows this blank screen. I can still do a swipe back gesture to go back to the previous screen.

Enclosed a quit dummy example video RPReplay_Final1571660466.MP4.zip

FYI: Video is captured from a real iPhone7 device with iOS13.1

Versions:

...
    "react": "16.9.0",
    "react-native": "0.61.1",
    "react-native-reanimated": "^1.3.0",
    "react-navigation": "^4.0.10",
    "react-navigation-redux-helpers": "^3.0.2",
    "react-navigation-stack": "^1.7.3",
    "react-navigation-tabs": "^2.5.0",
...

[hstorz]

@kamui545 yes I have almost same setup as you (using v8 instead of hermes) and also the problem looks similiar: blank page and bottom-tabs still visible. It works for me with none of 2.X versions I tried. And since some of my transitions look flickering on Android with 1.0.0.alpha23 I will now remove enableScreens for Android, on iOS I have no problem. What I also notice when using an 2.0.0.alpha my app crashes on the back navigation where usually the blank page appears with following crash:

AndroidRuntime java.lang.IllegalStateException: The specified child already has a parent. You must call removeView() on the child's parent first. AndroidRuntime at android.view.ViewGroup.addViewInner(ViewGroup.java:5106) AndroidRuntime at android.view.ViewGroup.addView(ViewGroup.java:4935)...

[AfrazHussain]

I can confirm that enableScreens() has been fixed in release 2.0.0-alpha.6 but the other issue about the nested stack screens still exists in Android.