iOS tabBar screen shows empty from time to time
Screen capture attached (easier than to explain 😊 )
I just ran the example, nothing more. Thank you.

What's rather interesting is I experienced this myself, but when I ran on device (another hurdle that needs to be overcome), I didn't experience it.
@lelandrichardson or whoever else would know, I've tracked it to this: at the time refreshTabViews (from signalFirstRenderComplete) is invoked on ReactTabBarController, the reactView has just the single root view that is a subview, but nothing else. None of the other content has rendered. When refreshing, you can actually log out the view hierarchy and see everything there. Perhaps signalFirstRenderComplete is being called too soon? Or something else I can't see?
I've implemented UISplitViewController support in a local branch, following the same pattern as the UITabBarController stuff. Seeing the same thing there, and it's really perplexing.
Any thoughts on how to fix this?
@benkraus did you manage to find a solution? And did it happen on a device any time after you commented here?
No solution yet, had it narrowed down really closely before I went on vacation. Picking it back up and trying to remember. 😃
Has there been any progress on this? Observing it myself in the simulator.
I struggled trying to get this fixed. 😢 There ended up being a lot of bugs with this lib, and it was fairly slow as far as progress goes/getting things merged etc, so we ended up writing our own native navigation library that is very much like a hybrid of this and Wix's react-native-navigation lib. It's working flawlessly. 😄 We plan on open sourcing it in a couple months when we have a little more time to clean things up.
Until then... Maybe the Airbnb guys could chime in here?
Last commit was 3+ weeks ago :(