Lots of crashes caused by OneSignal plugin on Google Play

We are running into lots of crashes related to oneSignal in our Google Play enviornment. 

App is built with Corona 2019.3549 (2019.11.9).

@OneSignal, can you help?

I am also running into these crashes. Between this and the issue above are 80~90% of my crashes.

java.lang.RuntimeException: at android.os.AsyncTask$3.done (AsyncTask.java:354) at java.util.concurrent.FutureTask.finishCompletion (FutureTask.java:383) at java.util.concurrent.FutureTask.setException (FutureTask.java:252) at java.util.concurrent.FutureTask.run (FutureTask.java:271) at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1167) at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:641) at java.lang.Thread.run (Thread.java:764) Caused by: java.lang.IllegalThreadStateException: at java.lang.Thread.start (Thread.java:724) at com.onesignal.OneSignalPrefs$WritePrefHandlerThread.startDelayedWrite (OneSignalPrefs.java:117) at com.onesignal.OneSignalPrefs.startDelayedWrite (OneSignalPrefs.java:183) at com.onesignal.OneSignal.setAppContext (OneSignal.java:602) at com.onesignal.NotificationBundleProcessor.ProcessFromGCMIntentService (NotificationBundleProcessor.java:64) at com.onesignal.GcmIntentJobService.onHandleWork (GcmIntentJobService.java:22) at com.onesignal.JobIntentService$CommandProcessor.doInBackground (JobIntentService.java:439) at com.onesignal.JobIntentService$CommandProcessor.doInBackground (JobIntentService.java:430) at android.os.AsyncTask$2.call (AsyncTask.java:333) at java.util.concurrent.FutureTask.run (FutureTask.java:266)

The SQLiteCantOpenDatabaseException seems to be just a single crash on a ChromeOS device. Running Android apps on ChromeOS is very new so it possible there is some stability for Chrome and device manufacturers to work out.

We do have thread open here about it you can follow through for some other devices seeing a similar issue.

https://github.com/OneSignal/OneSignal-Android-SDK/issues/945

For the IllegalThreadStateException WritePrefHandlerThread.startDelayedWrite issue please see the following comment on this thread for some things you can try:

https://github.com/OneSignal/OneSignal-Android-SDK/issues/917#issuecomment-600472976

We are looking to also release a Corona SDK update next week sometime with the noted changes in that thread.

@josh_OneSignal Thanks for the update. We can do another build and give it a try after the update to the SDK next week and let you know. thx!

I am also running into these crashes. Between this and the issue above are 80~90% of my crashes.

java.lang.RuntimeException: at android.os.AsyncTask$3.done (AsyncTask.java:354) at java.util.concurrent.FutureTask.finishCompletion (FutureTask.java:383) at java.util.concurrent.FutureTask.setException (FutureTask.java:252) at java.util.concurrent.FutureTask.run (FutureTask.java:271) at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1167) at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:641) at java.lang.Thread.run (Thread.java:764) Caused by: java.lang.IllegalThreadStateException: at java.lang.Thread.start (Thread.java:724) at com.onesignal.OneSignalPrefs$WritePrefHandlerThread.startDelayedWrite (OneSignalPrefs.java:117) at com.onesignal.OneSignalPrefs.startDelayedWrite (OneSignalPrefs.java:183) at com.onesignal.OneSignal.setAppContext (OneSignal.java:602) at com.onesignal.NotificationBundleProcessor.ProcessFromGCMIntentService (NotificationBundleProcessor.java:64) at com.onesignal.GcmIntentJobService.onHandleWork (GcmIntentJobService.java:22) at com.onesignal.JobIntentService$CommandProcessor.doInBackground (JobIntentService.java:439) at com.onesignal.JobIntentService$CommandProcessor.doInBackground (JobIntentService.java:430) at android.os.AsyncTask$2.call (AsyncTask.java:333) at java.util.concurrent.FutureTask.run (FutureTask.java:266)

The SQLiteCantOpenDatabaseException seems to be just a single crash on a ChromeOS device. Running Android apps on ChromeOS is very new so it possible there is some stability for Chrome and device manufacturers to work out.

We do have thread open here about it you can follow through for some other devices seeing a similar issue.

https://github.com/OneSignal/OneSignal-Android-SDK/issues/945

For the IllegalThreadStateException WritePrefHandlerThread.startDelayedWrite issue please see the following comment on this thread for some things you can try:

https://github.com/OneSignal/OneSignal-Android-SDK/issues/917#issuecomment-600472976

We are looking to also release a Corona SDK update next week sometime with the noted changes in that thread.

@josh_OneSignal Thanks for the update. We can do another build and give it a try after the update to the SDK next week and let you know. thx!