Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The Debug version of Android APP crashes on startup #3638

Open
Tuning3DT opened this issue Jan 10, 2025 · 4 comments
Open

The Debug version of Android APP crashes on startup #3638

Tuning3DT opened this issue Jan 10, 2025 · 4 comments
Labels

Comments

@Tuning3DT
Copy link

The Debug version of Android APP crashes on startup. The release version works fine.
AIRSDK MacOS 51.1.3.3
Android SDK 35
I attached the logcat output.
logcat_output.txt.zip

@Tuning3DT Tuning3DT added the Bug label Jan 10, 2025
@ajwfrost
Copy link
Collaborator

Interesting call stack..

01-09 17:44:20.424 19038 19038 I AdobeAIR: Exception caught from Java: java.util.ConcurrentModificationException
01-09 17:44:20.424 19038 19038 F tuning.Tuning3D: java_vm_ext.cc:598] JNI DETECTED ERROR IN APPLICATION: jarray was NULL
01-09 17:44:20.424 19038 19038 F tuning.Tuning3D: java_vm_ext.cc:598]     in call to GetArrayLength

So, there is C++ code calling Java code which has thrown an exception, but the C++ code then doesn't protect against the fact we didn't get an array object hence is just calling GetArrayLength(null) which crashes it.

I'm not 100% sure how a ConcurrentModificationException is being thrown, although it might be this is related to some changes we made to remove out-dated APIs a couple of months ago.. we can protect against the error/crash but I would prefer we also prevented that Java exception in the first place..

thanks

@Tuning3DT
Copy link
Author

@ajwfrost Thanks for replying.
Should I use an older SDK version for now?
From which version were those changes made?

@ajwfrost
Copy link
Collaborator

Yes an older version should work, the updates that I think may have broken this were in 51.1.1.5 so if you use 51.1.1.4 or earlier, it should be okay..

@Tuning3DT
Copy link
Author

Thanks @ajwfrost , it worked when I used 51.1.1.4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants