You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I also tried looking into what in the library code could have caused the issue. Just adding the console.log below means the backdrop then does work:
I've tried moving the modal onto different screens in our app and the behaviour is always the same.
I have also tried using the Flipper layout debugger to see if the modal is just invisible or not there at all. It looks like this same View is shown whether the bug is present or not:
=> so I guess the backdrop must be hidden vs not there?
I tried the suggestion to switch for react native modal, however the backdrop behaviour is different so not really applicable to this particular problem
Reproducible Demo
I'm afraid this is a little tricky. It seems very tied to the particular context of our codebase, which I can't share. The app isn't super quick on android, so I wonder if the bug happens because of a race condition that rears its head when there are performance bottlenecks? The fact that adding a console.log fixes it suggests something along those lines.
I had a look into the source code to look for any clues...could the fact makeBackdropruns in the render function cause any issues? Is there anything stateful happening there?
Let me know if there's anything else I can try. Thanks!
The text was updated successfully, but these errors were encountered:
Environment
Platforms
Android
Versions
Description
I have a screen with a Modal on it, which is set to appear immediately (i.e. isVisible is true on the first render)
The problem can be summarised as (on Android):
Works (backdrop shows)
Doesn't work (backdrop doesn't show)
Some more info....
Here is my modal config:
When the modal doesn't work, isVisible is true in the first render of the screen.
If I set a timeout before setting isVisible, the backdrop works. e.g.
I also tried looking into what in the library code could have caused the issue. Just adding the console.log below means the backdrop then does work:
I've tried moving the modal onto different screens in our app and the behaviour is always the same.
I have also tried using the Flipper layout debugger to see if the modal is just invisible or not there at all. It looks like this same View is shown whether the bug is present or not:
=> so I guess the backdrop must be hidden vs not there?
I tried the suggestion to switch for react native modal, however the backdrop behaviour is different so not really applicable to this particular problem
Reproducible Demo
I'm afraid this is a little tricky. It seems very tied to the particular context of our codebase, which I can't share. The app isn't super quick on android, so I wonder if the bug happens because of a race condition that rears its head when there are performance bottlenecks? The fact that adding a console.log fixes it suggests something along those lines.
I had a look into the source code to look for any clues...could the fact
makeBackdrop
runs in the render function cause any issues? Is there anything stateful happening there?Let me know if there's anything else I can try. Thanks!
The text was updated successfully, but these errors were encountered: