-
-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
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
Screen with WebView crashes App during navigation #9061
Comments
The versions mentioned in the issue for the following packages differ from the latest versions on npm:
Can you verify that the issue still exists after upgrading to the latest versions of these packages? |
Sorry that was a typo. It is version 5.12.6 |
Do you use |
@WoLewicki No I never used |
@chongma it depends on how you created the project. You can check if |
See the workaround here #9067 (comment) |
Hi Matthew(chongma), Regards, |
Hey! This issue is closed and isn't watched by the core team. You are welcome to discuss the issue with others in this thread, but if you think this issue is still valid and needs to be tracked, please open a new issue with a repro. |
@chongma |
Thanks @rezareact That worked, on IOS and Android! |
the solution works on my android, but is possible that the crash occurs only on some devices with com.google.android.webview instead of devices with com.android.chrome? |
@chongma Thank you for your workaround! Seems to still be an issue |
@lennartkloock We tried all proposed solutions and were still getting crashes on certain Android devices. This is what we did to fix it temporarily: Use the useIsFocused hook to render the WebView conditionally.
We had one screen where we had to wrap the parent component (instead of the child component containing the WebView) in isFocused to avoid a crash. This is not an optimal solution, but fortunately we didn't experience any noticeable decline in performance. |
Solved with:
|
The only reasonable workarounds I've found acceptable (without disabling the animations on the stack screen) are:
NOTE: I could see some noticeable performance regression with the latter option, so I'd suggest to try the former first! |
Issue resolved |
Current Behavior
Navigating to a screen which contains a WebView crashes the whole app with no stack trace. Disabling animations on the screen fixes the problem e.g. <Stack.Screen ... options={{animationEnabled: false}} />
Expected Behavior
It should navigate
Your Environment
The text was updated successfully, but these errors were encountered: