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 really like this library, and it works fine with RN 0.60+ on both iOS and Android. However, on Android, some devices have this weird problem that when you trigger the overlay, the background of the overlay (which should be a plain color) has what seems to be traces of the previously visited screen. I'm using react-navigation.
For clarity, suppose you have a FlatList on Screen A. You click on a FlatList item and it opens Screen B, which then shows an overlay (from this library). On Android, you will see the blurred screen on top of Screen B, but there will be traces of Screen A (some sort of misrendering) with edges and colors belonging to, say, the FlatList on Screen A. The behavior is strange. I wonder if anyone else has run into this before and whether there's a solution. I worry that this repo is incompatible with react-navigation.
The text was updated successfully, but these errors were encountered:
I think it's related to how this library works . It takes screen shot of previously root view and applies blur effect on it. You see this issue when you navigate to new page and open dialog immidiatly , but it's not big deal
I really like this library, and it works fine with RN 0.60+ on both iOS and Android. However, on Android, some devices have this weird problem that when you trigger the overlay, the background of the overlay (which should be a plain color) has what seems to be traces of the previously visited screen. I'm using react-navigation.
For clarity, suppose you have a FlatList on Screen A. You click on a FlatList item and it opens Screen B, which then shows an overlay (from this library). On Android, you will see the blurred screen on top of Screen B, but there will be traces of Screen A (some sort of misrendering) with edges and colors belonging to, say, the FlatList on Screen A. The behavior is strange. I wonder if anyone else has run into this before and whether there's a solution. I worry that this repo is incompatible with react-navigation.
The text was updated successfully, but these errors were encountered: