SIGABRT errors on Samsung devices only & on OS 12 only

[dampgnat]

Stability on Android has dropped significantly from 98.5% to 90% since updating from AIR_SDK_33.1.1.620 to AIR_SDK_33.1.1.779 (iOS is unaffected)

Bugsnag reports these new crashes affect Samsung devices only and on OS 12 only:

SIGABRT AIRAppEntry

Stack trace: /apex/com.android.runtime/lib64/bionic/libc.so:334624 abort

Breadcrumb shows "Orientation changed" happens right before the abort.

SIGABRT /apex/com.android.runtime/lib64/bionic/libc.so:334624 (The long number at the end varies a lot)

Stack trace: SIGABRT Abort program /apex/com.android.runtime/lib64/bionic/libc.so:331792 abort /apex/com.android.art/lib64/libart.so:7148928 art::Runtime::Abort(char const*) /apex/com.android.art/lib64/libbase.so:92512 0x7a3fe98960 /apex/com.android.art/lib64/libbase.so:90000 android::base::LogMessage::~LogMessage() /apex/com.android.art/lib64/libart.so:2643952 art::JavaVMExt::AddGlobalRef(art::Thread*, art::ObjPtrart::mirror::Object) /apex/com.android.art/lib64/libart.so:5877204 0x773879add4 ...... etc.

No breadcrumbs immediately before abort.

[ajwfrost]

It looks like these are related to the new font handling - particularly if on Android OS 12 -> are you able to update to the 33.1.1.821 build please? There were a couple of issues in 779 relating to the JNI references which look like this, plus one instability relating to text fields that had areas outside of the stage, all of which were fixed in 795 (but we had an issue in 795 where re-orienting the phone in 'direct' mode caused a problem..)

thanks

[dampgnat]

Client app updates can take weeks to go through, so it will be a while before I get results. Will let you know.

Thanks Andrew!

[dampgnat]

I can confirm that Android user stability has improved from 89.5% to 99.5% after updating from AIR SDK 33.1.1.779 to 33.1.1.821

Fantastic!!