"This app has a bug." Android 12 error

kupo_games

Hey guys, since I updated my app to a newer version of AIR for Android (33.1.1.743), many newer Samsung devices have been unable to start my game. Some examples include the Note 10, s20, s20 ultra, s20 FE, and S21+.

The error message is just "Something went wrong with [App]. [App] closed because this app has a bug. Try updating this app after its developer provides a fix for this error.", and then the app fails to start.

Has anyone seen this before? I'll try rolling back to an older version of AIR to see if it helps.
I guess I should post this on the AIR GitHub?

Thanks.

FliplineStudios

I've had immediate crashes with the new Beta 33.1.1.758 (specifically with GPU render mode), but I haven't had any crashes at startup with 743... though I also haven't tried on any of those Samsung devices. Probably a good idea to post to the GitHub!

kupo_games

FliplineStudios
I definitely need that GPU render mode - I'm totally relying on it!
Luckily I've got a pretty large tester group, my game is in Open Testing and has over 3,000 users, so I'm fairly sure it starts correctly for most people. It's just such a pain that it takes so long to upload and review each new version, just to test some minor changes!

FliplineStudios

@kupo_games Same here, hopefully they can get that beta 758 straightened out with GPU mode! These startup crashes are happening for you with 743 though right? Do you have any of those Samsung devices yourself to check logcat for more details about the crash, or just heard from your users testing it on those devices?

FliplineStudios

@kupo_games Quick follow-up: I just installed your early access game on my Pixel 4 running Android 12 and gave it a shot, and it did crash for me too with this error in logcat:

java.lang.IllegalArgumentException: air.EpicBattleFantasy5: Targeting S+ (version 31 and above) requires that one of FLAG_IMMUTABLE or FLAG_MUTABLE be specified when creating a PendingIntent.

Not sure if you're using any ANEs and if there's any incompatibility with any of them with Android 12 / SDK 31, but if you do post to the AIR GitHub it might be worth posting your application xml there as well in case there's something that needs to be configured for this PendingIntent issue in Android 12 in it. Feel free to PM me here or email (mneff@flipline.com) if you'd like me to send over a logcat log or anything else I can do to help!

kupo_games

FliplineStudios
It works correctly on my Note 8, but I tried it on my partner's S21, and it does indeed crash on startup there.
Is there any simple way to see the logcat files? I'd rather not install developer tools on her phone...

Thanks for sharing that error message! I haven't added any new ANEs since the previous version, and I don't think I've changed the XML file either. I'll investigate and try running different versions on my partner's phone. I'm really curious as to what change may have caused this, but with that tip I should be able to narrow it down...

Edit: I'm using Distriqt's ANEs for In-App purchases, Adverts, and Play Services/Achievements. That Adverts one in particular adds a huge wall of text to the XML...

FliplineStudios

Hmmm I've always just turned on Developer Options on the phone (Settings > About Phone > Software Information > Tap Build Number a bunch of times), then connected it to the PC with a USB cable and allowed debugging over USB, then opened a command prompt with adb logcat to see what the phone is saying. Not sure if there are any good ways to view the errors on the device itself... though at least you can easily turn off Developer Options on the phone later when you're done testing.

Android 12 does have some new stricter requirements with intent-filter, and possibly an older ANE that isn't updated for Android 12's new requirements may need some adjustments, not entirely sure though! I just updated all of our ANEs to the newest available versions while I'm working through the new AIR SDK update and AABs.

FliplineStudios

Any chance you're using Distriqt's Share ANE? I do also see in the error log something about a DropBox intent (which Share ANE uses), and they did update the Share ANE late last year with some Android security updates (in both the ANE itself and also the XML formatting)

kupo_games

FliplineStudios Nope, I'm not using the Share ANE.
Googling around has given me some possible solutions to try - some say I need to change some Gradle settings.
I'm sure the solution is something fairly simple, I'm just not familiar with all of this technical Android stuff!
Doing Flash games for Desktop was so much more straightforward!
Anyway, thanks for the help. I'll update this post when I find a solution.

FliplineStudios

Yeah, Android development with AIR has gotten much more complicated lately, it's definitely stressful! Good luck with tracking down the issue!

Abdullah_kk

kupo_games
FliplineStudios
Did you find any solution?
I'll be thankful if you can share it..
thanks

ma

Highly recommend making sure you set the target sdk to 30 currently. 31 is still a little experimental with AIR and definitely our ANEs haven't been updated to support it yet. There are a lot of changes required for Android 12 (API 31) that I'm working through.

Often simply setting the targetsdk will alleviate a lot of issues. Add something like the following to your manifest additions:

<uses-sdk android:minimumSdkVersion="19" android:targetSdkVersion="30" />

kupo_games

ma
Adding that line fixed the problem on my partner's device - thanks!
I'll go ahead and roll out an update and hopefully it'll work for everyone else too.

ma

Also really worth grabbing the logs from a device that crashes as @FliplineStudios suggests. You'll nearly always have the reason for the crash in the logs.

ma

Good to hear,

We are expecting to have Android 31 compatible versions of all our extensions within the next month.

Cheers

kupo_games

Abdullah_kk Yeah, adding that line to my manifest file to not target Android 12 fixed it for now.
It was only the newest phones that were having issues.

<uses-sdk android:minimumSdkVersion="19" android:targetSdkVersion="30" />

kiwicode

any news regarding this issues? With Google enforcing apps to be updated to the latest two SDK versions I guess it should be a top priority

ma

Pretty sure everything is working fine with Android 12 now . Are you having an issue?