Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Toast and ActionSheet both cause crashes on call

See original GitHub issue

Hey there,

First of all, great project here. Makes prototyping very quick and basically has almost everything you need for your production application.

However there is two components that are causing me issues (and I see them logged in Firebase Crashlytics a lot) and that is the Toast and ActionSheet.

Looking through the issues on this repo, every time it is brought up, it is said that you just have to add <Root> as your top-most component to your application.

Whilst this does work a lot of the time, almost all of the time, there is a specific set of instructions, in a specific order that causes a cannot call show on undefined. This happens to both the Toast and ActionSheet

There have been work arounds suggested, and multiple issues opened and subsequently closed on this particular issue but I am not convinced any of the suggested workarounds have actually worked for very long.

react-native 0.52.0 react 16.3.2 native-base 2.4.3

Is the bug present in both ios and android or in any one of them? Both

I am following the documentation directly, my topmost component’s first child is <Root> and the rest of my application is inside of that, including navigation, redux providers, etc.