Note to everyone: You can download old APKs from the releases page on Google Dev Console, run on device and view output with adb logcat
We have had 486 reports in the last 7 days of this CRASH. PLEASE FIX IT ASAP. (This was posted in another thread, and has not been dealt with in over a week)
We really hope this is expedited soon.
All of our Corona based apps that have had crash issues have dived in ranking on the google play store. This is the reality of revenue and sales hurt over these crashes.
We have unity based apps on the store which don’t have this amount of crash issues. C’mon guys, I realize you have a lot to do, but at the very least, these issues need to be taken care of.
java.lang.IllegalStateException :
at android.app.FragmentManagerImpl.checkStateLoss (FragmentManager.java:1323)
at android.app.FragmentManagerImpl.popBackStackImmediate (FragmentManager.java:493)
at android.app.Activity.onBackPressed (Activity.java:2304)
at android.app.Activity.onKeyUp (Activity.java:2282)
at com.ansca.corona.CoronaActivity.onKeyUp (CoronaActivity.java:3482)
at android.view.KeyEvent.dispatch (KeyEvent.java:3232)
at android.app.Activity.dispatchKeyEvent (Activity.java:2512)
at com.ansca.corona.input.RaiseKeyEventTask$1.run (RaiseKeyEventTask.java:90)
at android.os.Handler.handleCallback (Handler.java:733)
at android.os.Handler.dispatchMessage (Handler.java:95)
at android.os.Looper.loop (Looper.java:136)
at android.app.ActivityThread.main (ActivityThread.java:5584)
at java.lang.reflect.Method.invokeNative (Native Method)
at java.lang.reflect.Method.invoke (Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:1268)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1084)
at dalvik.system.NativeStart.main (Native Method)
Hey JBean, please, refrain from using ALL CAPS.
Can you reproduce the crash? Do you have any information why it happens? Also, 486 doesn’t mean much. If you have 1m sessions, it’s like 0.05%.
We do not use Fragments or FragmentManager inside Corona which seem to be causing this crashes. Lot of ad networks and other plugins use them. I suggest trying your app, pressing back button and look for the crash while various ads are playing.
@vlads: Sorry I was copying and pasting something and that happened to be the text that was auto-typing from a prior message. (It somehow copied the same font style as the code I pasted)
I haven’t been able to reproduce the crash on my device.
What I am speculating is that the users are trying to hit the back button to back out of the ads showing up. We are noticing significant delays with the very first ad that shows up from the Applovin plugin (not sure if this is an Applovin thing, or a preload issue)
So what is happening is, when the first ad shows up with Applovin paid plugn, there is a black screen for about 3-4 seconds, then the ad finally appears (This only happens with the first ad) subsequent ads show up as normal.
So what I am speculating due to this issue is that users are possibly tapping the back button to get out of the ad, and there’s no response, and it inadvertently exits out of the app.
I tested the app myself, and unless I repeatedly tap the back button, it does not crash. So I’m not sure if it’s user behavior that’s getting inputted as a crash.
How do we prevent this error from happening then? What is your solution?
Thanks Vlad! Let me know if you have any ideas on how to fix it.
Also, what version of the Applovin SDK is implemented in the paid applovin plugin right now? According to Applovin, the latest SDK version for android is 8.0.0
That latest version is currently out, so hoping that this new one may fix that black screen issue on the first ad impresion, which may inadvertently fix the issue above that I have described.
Can I get full list of plugins you’re using?
Admob paid and Applovin paid are the only 2 plugins we use.
Also, did you guys see this new EU rule for Applovin? They said we now have to indicate this below. Is this something you guys need to add to the plugin, or do we have to specify this in the app itself?
https://www.applovin.com/integration#androidPrivacySettings
Privacy Settings
AppLovin SDK requires that publishers set a flag indicating whether the user has provided opt-in consent for the collection and use of personal data.
If the user has consented, please set the following flag to true.
AppLovinPrivacySettings.setHasUserConsent( true, context );
If the user has not consented, please set the following flag to false.
AppLovinPrivacySettings.setHasUserConsent( false, context );
Additionally, if the user is known to be in an age-restricted category (i.e., under the age of 16) please set the following flag to true.
AppLovinPrivacySettings.setIsAgeRestrictedUser( true, context );
This is something you as the developer will have to code for.
JBean, we’re working on it. Please, refrain from anything but Crashes & ANRs in this thread.
Btw, by plugins, I mean all plugins, not just ad plugins.
So all plugins:
Applovin Paid
Admob Paid
Google iAP
Those are the 3 plugins we use for all android apps consistently.
Got it on the other topic.
Thank you!
Hey, JBean. While we wasn’t able to figure out which exact thing causes that exception, we put blanket try/catch around pause routine in 3281. This should prevent crashes.
@vlads - thanks for the update.
I think I may have figured out the difference between using the back arrow with Corona built apps, and using it with unity built ones.
When you tap the “back” button on the device in a corona built app (even the latest build that you guys updated) it immediately exits out of the app.
With Unity based apps, tapping the back arrow repeatedly on the device does not allow you to exit the app. You have to physically disable the window in order to exit. This requires using the “recents” button, the one that shows all the windows that were recently open, including apps.
I think in order to eliminate any crashes detected by the user using the back arrow, it has to be disabled as a method of exiting the app. Not sure if this makes sense or is feasible, but just something I noticed this morning when testing both Corona and Unity based apps.
Is there a way for Corona to hijack the “back” button on a device so that it doesn’t exit out of the app when pressed?
you can easily customize what happens when you press back button on Android. On top of my head, should be something like
[lua]function scene:key(event)
if event.keyName == “back” then
… do some stuff here? …
return true
end
end
Runtime:addEventListener( “key”, scene )[/lua]
@vlads, we’ll give that a try.
Regarding the Applovin PAID plugin - what version of the Applovin SDK is implemented currently for android and iOS?
It looks like AppLovin paid is using 7.8.6 and was updated April 17, 2018.
Rob
Of course. But so far it was rather frustrating (exploring crash tracebacks ofter is).
But, here’s some good news: next daily build would contain some experimental fixes for bitmap related crashes. I would appreciate if someone to test those fixes. Build number should be 3169.
Hey, [member=‘Fungrip’] and [member=‘Davebollinger’]!
You both posted tracebacks with bitmap stuff in them. I introduced some experimental changes (nothing dangerous) in 2017.3169 which may fix them. Is there a chance you could try them? I still could not reproduce any of the issues.
It may take a couple days, but yes I’ll test it, rebuild/update with 3169 (or whatever latest on that day). But even then, it may take a while to get enough data to show anything (given that the TOTAL for all crashes is only ~1.5% and I’m in the same boat as you as far as not knowing what specifically would reproduce them)
@vlads will do, and we are in the same boat as you and dave in that we are unable to reproduce it so far.