-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Crash at HeadlessInAppWebView dispose #881
Comments
👋 @dodatw NOTE: This comment is auto-generated. Are you sure you have already searched for the same problem? Some people open new issues but they didn't search for something similar or for the same issue. Please, search for it using the GitHub issue search box or on the official inappwebview.dev website, or, also, using Google, StackOverflow, etc. before posting a new one. You may already find an answer to your problem! If this is really a new issue, then thank you for raising it. I will investigate it and get back to you as soon as possible. Please, make sure you have given me as much context as possible! Also, if you didn't already, post a code example that can replicate this issue. In the meantime, you can already search for some possible solutions online! Because this plugin uses native WebView, you can search online for the same issue adding Following these steps can save you, me, and other people a lot of time, thanks! |
I am getting this also in release mode. In the debug, there is no problem. I am also using headless. |
@aamir-nazir found any fix? |
found any fix? |
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug and a minimal reproduction of the issue. |
This issue happen when we upgrade inappwebview from 4.0 to 5.36.
I cannot reproduce this issue, the crash come from end user by crashlytics.
This issue happen when we call HeadlessInAppWebView.dispose().
We try to publish a version that don't call HeadlessInAppWebView.dispose(). this issue not happen
But I don`t think it is good idea.
Here is crash log
The text was updated successfully, but these errors were encountered: