You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by GitBox <gi...@apache.org> on 2020/11/25 11:16:28 UTC

[GitHub] [cordova-android] Reqwy edited a comment on issue #1000: exception throwed when cordovaActivity destroy

Reqwy edited a comment on issue #1000:
URL: https://github.com/apache/cordova-android/issues/1000#issuecomment-733597407


   > It's a bit embarrassing. Under the latest Cordova project(a demo), I destroy the Cordova page and still report that exception. However, I found that my previous inference was not true, that is, Cordova's closing affected the setflag setting of the next page.
   > cordova -v 9.0.0 (cordova-lib@9.0.1),Installed platforms: android 8.1.0
   > the excption stacktrace is different than before
   > 
   > 2020-06-17 16:04:22.328 15867-15867/i W/cr_AwContents: Application attempted to call on a destroyed WebView
   > java.lang.Throwable
   > at org.chromium.android_webview.AwContents.a(PG:124)
   > at vo.loadingStateChanged(PG:2)
   > at android.os.MessageQueue.nativePollOnce(Native Method)
   > at android.os.MessageQueue.next(MessageQueue.java:363)
   > at android.os.Looper.loop(Looper.java:173)
   > at android.app.ActivityThread.main(ActivityThread.java:8178)
   > at java.lang.reflect.Method.invoke(Native Method)
   > at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:513)
   > at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1101)
   > 
   > what a strange thing is the phenomenon below is still exist in my app,but not in the demo
   > "I found the cordova code where the exception was thrown (CordovaWebviewImpl#handleDestroy) and commented out the code that caused the exception (this.loadUrl("about:blank");). There will be no above problems, and my setFlags function normally"
   
   Can confirm that. cordova-android 9.0.0 with android 9.0.0,  targetSdk set to 29 or 30 (reproduced on both), but bug is there on all devices starting with API 24+ (didn't test for lower)
   
   Commenting out the line that @zhqcqupt mentioned makes that exception disappear. 
   
   Is there a less hacky way though to bypass it?


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org