-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Probable deadlock detected due to WebView API being called on incorrect thread while the UI thread is blocked #2806
Comments
This does not look related to |
Hello 👋, this issue has been opened for more than 2 months with no activity on it. If the issue is still here, please keep in mind that we need community support and help to fix it! Just comment something like still searching for solutions and if you found one, please open a pull request! You have 7 days until this gets closed automatically |
Suddenly this started happening on our app, only on Android 10 devices. I am saying suddenly because we are running webview for 2 years and this is the 1st time we see this persisting issue. Moreover it started happening out of the blue, because we have not put changes in our Webview implementation for many months now. Is there some solution to fix/bypass this crash |
Yes, this error is actual, we strated getting 10-15 crashes per week on Android 10 devices @TheAlmightyBob @Vatousiadis Crash:
Stack:
|
One of the possible solutions is to create a File: Change: import android.os.Looper;
// ....
protected static class RNCWebView extends WebView implements LifecycleEventListener {
// ....
@Override
public boolean onCheckIsTextEditor() {
if (Looper.myLooper() == Looper.getMainLooper()) {
return super.onCheckIsTextEditor();
} else {
return false;
}
}
} |
But seems like it doesn't work |
Yes, I implemented it in my app (https://bit.ly/Tik_Downloader), but the error persists 😕 |
same for me, android 10 crash on webview |
Taking into account that That is why the possible solution can be to add the following file:
It must be in the package |
Hi,
I am getting a crash report on production
I don't know how to reproduce
Environment:
The text was updated successfully, but these errors were encountered: