After upgrading native-base to 2.8.0, Toast component dosen't show up. After several attempts some fade is noticeable. It seems like toast's close method is execute immediately after showing up, duration set in config object is ignored.
react-native: 0.57.0
react: 16.5.1
native-base: 2.8.0
Occurred on Android (not checked on iOS)
Verified, all good with Toast on iOS and Android
I also encountered this problem.
*
react-native: 0.57.4
react: 16.6.0-alpha.8af6728
native-base: 2.8.1
*
I forgot to add that issue occurred on Android 6.0
Currenlt experiencing this now with
RN: 0.57.5
NB: 2.8.1
React: 16.6.1
This is the unhandled rejection error i get

From the docs:
For
Toastto work, you need to wrap your topmost component inside<Root>from native-base.
I must admit I had also skipped this and had jumped straight to the "styled Toast" section. An idea would be to throw an error saying Did you forget to wrap your App component in <Root>? (see https://docs.nativebase.io/Components.html#toast-def-headref)
I'm experiencing an inssue that sometimes it shows for less time then the duration, i.e. duration 5000 doesn't even shows up and duration 10000 shows for like 2sec,
Not sure if it's a native base problem or something to do with the clock discrepancy between connected phone and node running PC.
Not sure if it will happen in the production release.
In either way, do you guys have any thoughts in how to handle this beforehand ?