We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
On a promise resolution from a fetch call, I do two things:
fetch
react-native-navigation
Navigation.showModal(...)
I have found that having (1) here means the modal is immediately hidden, right after being presented.
Any ideas what could be going wrong here, and how these two things can be reconciled?
I tried a setTimeout with low timeout > 0 and it works... sometimes. So it leads to non-deterministic behaviour.
setTimeout
> 0
The text was updated successfully, but these errors were encountered:
Same issue here!!!!!
Sorry, something went wrong.
FYI I wasn't able to resolve this any other way, and simply stopped using this library.
I ended up simply creating my own overlay, and simply displaying is as an Overlay with react-native-navigation, which ended up being really easy.
Here's a gist of my code which you could adapt: https://gist.github.com/elsurudo/0cc2edb118d63370f086cb5a8b1b0e00
You would just need to register the component in the typical RNN way.
No branches or pull requests
On a promise resolution from a
fetch
call, I do two things:react-native-navigation
modal usingNavigation.showModal(...)
I have found that having (1) here means the modal is immediately hidden, right after being presented.
Any ideas what could be going wrong here, and how these two things can be reconciled?
I tried a
setTimeout
with low timeout> 0
and it works... sometimes. So it leads to non-deterministic behaviour.The text was updated successfully, but these errors were encountered: