I use pushwoosh, another bug is notification events received on Android 8+ but not shown on status bar.
Yes @robmiracle Notifications v2 (this is a change) and OneSignal (no changes on this front).
Also note that OneSignal notifications are getting through to the new build.
So OneSignal came back with…
"Are you only seeing this on Android 8+ devices? What Android API level are you targeting? This is the targetSdkVersion in you build.gradle. Our current Corona SDK is only compatible with 25 and lower at this time. Lower it to 25 will allow your app to run on Android Oreo 8+ devices until we update our SDK.
We are looking to update our Corona SDK to match closer to our native Android SDK in an update next month which will allow targetSdkVersion 26+."
It is 8+ devices that we’re seeing with the problem. Question is how do we change the target version in the Corona build process @robmiracle ?
You can roll-back to the last version of Corona before we released support for API level 27. The last public build, 3326 is the first version where we switched from 25 to 27. However, we have fixed a lot of ANR and Android crash problems in builds since 3326. You may be trading one problem for a host of others.
Also, I know for certain you cannot submit new apps that don’t support 26+ and I’m pretty sure the window for updating apps with older versions has not passed. I don’t believe that Google will allow apps that don’t support 26+ any longer.
You are welcome to try to roll back to 3325 or earlier, but I’m not sure I would recommend that course of action. My recommendations are:
-
Wait on OneSignal’s update. I can’t even begin to guess when that will be. Keeping pressure on this may speed things up.
-
Implement OneSignal’s REST-based system. I’m not familiar with the process, but I know other community developers have worked this out and you can search the forums on how to do this.
-
Consider another provider.
Rob
@Rob Miracle I believe the java.lang.IllegalStateException is being thrown from com.ansca.corona.SystemStartupBroadcastReceiver.onReceive based on @beernathan stack trace. So this looks to be something from Corona itself or one of Corona’s Notification plugins, either V1 or V2.
The same stack trace was also reported by @zdmitrynsk on another thread;
https://forums.coronalabs.com/topic/72988-onesignal-with-targetsdkversion26-getting-error-background-start-not-allowed-service-intent-cmpcomonesignalgcmintentservicehas-extras/?p=390287
@karpovpw (Corona Staff) replied back with this update in Oct but no update since;
Thanks.
Looks like it’s back to you @robmiracle
Hey @robmiracle - do you agree with the assessment from OneSignal?
Feel like we’re stuck between a rock & a hard place here.
It appears that you’re saying we can’t release an app right now that has both OneSignal and Notifications?
I’m checking…
Ping… this is still a big problem @robmiracle
This is now getting very frustrating. We re-coded to go to the OneSignal REST API (not the plugin) and re-released. We only have Notifications v2 now and we’re still getting this crash on android all the time (Corona 3326):
java.lang.RuntimeException :
at android.app.ActivityThread.handleReceiver (ActivityThread.java:3399)
at android.app.ActivityThread.-wrap18 (Unknown Source)
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1780)
at android.os.Handler.dispatchMessage (Handler.java:105)
at android.os.Looper.loop (Looper.java:164)
at android.app.ActivityThread.main (ActivityThread.java:6944)
at java.lang.reflect.Method.invoke (Native Method)
at com.android.internal.os.Zygote$MethodAndArgsCaller.run (Zygote.java:327)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1374)
Caused by: java.lang.IllegalStateException :
at android.app.ContextImpl.startServiceCommon (ContextImpl.java:1538)
at android.app.ContextImpl.startService (ContextImpl.java:1484)
at android.content.ContextWrapper.startService (ContextWrapper.java:663)
at android.content.ContextWrapper.startService (ContextWrapper.java:663)
at com.ansca.corona.SystemStartupBroadcastReceiver.onReceive (SystemStartupBroadcastReceiver.java:29)
at android.app.ActivityThread.handleReceiver (ActivityThread.java:3392)
Ding
I’ve asked engineering to look into this as soon as possible.
Rob
Thanks Rob - appreciate it.
Just to recap - here are our current plugins on Android…
[“plugin.gameanalytics”] =
{
publisherId = “com.gameanalytics”,
},
– [“plugin.OneSignal”] =
– {
– publisherId = “com.onesignal”,
– },
[“plugin.advertisingId”] =
{
publisherId = “com.coronalabs”
},
[“CoronaProvider.native.popup.social”] =
{
publisherId = “com.coronalabs”
},
– [“CoronaProvider.native.popup.activity”] =
– {
– publisherId = “com.coronalabs”
– },
[“plugin.notifications.v2”] =
{
publisherId = “com.coronalabs”
},
[“plugin.googleAnalytics”] =
{
publisherId = “com.coronalabs”,
supportedPlatforms = { iphone=true, android=true, }
},
[“CoronaProvider.analytics.flurry”] =
{
publisherId = “com.coronalabs”,
supportedPlatforms = { iphone=true, android=true }
},
[“CoronaProvider.gameNetwork.google”] =
{
publisherId = “com.coronalabs”,
supportedPlatforms = { android=true }
},
[“plugin.CoronaSplashControl”] =
{
publisherId = “com.coronalabs”
},
Yes, the problem seems to be in the new corona 3326 itself. We have around 20-25 apps on Store and as Google said support API level 26+ support then we updated corona and start updating apps, we have just updated 4 or 5 i think yet and were checking stats. Its horrible our crash rate increased a lot, previously it was close to 99.9, 99.8 and so on and now its around 98, 97 and even 96 on one app.
We have used plugins like Admob, Notifications V2, GPGS v2 and splash screen control.
Note: No change has been done in build other than just taking build with the new Corona sdk 3326.
Please anyone if know how to solve this, please comment below so all can get the benefit from it.
What happens if you use the latest daily build?
Rob
So we pushed out a release based on 3462 on Feb 7 with a 50% rollout. It’s the 12th now so we are 5 days in.
Reporting on the Google Play console is with last 1 day or last 7 days, so not enough granularity, but…
1 day
3326: 17 IllegalStateException
3462: 0 IllegalStateException
7 day
3326: 69 IllegalStateException
3462: 0 IllegalStateException
Looking good on the latest build! Will give it a couple more days then crank it up to a full rollout.
NOTE: This is all using the OneSignal REST API (not the plugin). Would be great to see this same experiment with the plugin.
Still no IllegalStateExceptions. 30 day crash rate slowly dropping… down to 6.21%
Hi, good to hear that.
Does anyone have an experience with OneSignal Plugin? I would prefer not to rewrite it to REST API.