-
Notifications
You must be signed in to change notification settings - Fork 11
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
split_config.arm64_v8a.apk!libCore.so crash #2754
Comments
Air SDK:- 50.2.3.3 pid: 0, tid: 31055 >>> com.iz.... <<< backtrace: |
same issue occured. |
I use AIR 50.2.2.6 There are also similar problems @ajwfrost |
Hi We had an issue with JNI references that we believe is the culprit for these issues, which was addressed in release thanks |
we are seeing similar problems using AIR 50.2.3.5 pid: 0, tid: 26853 >>> air.de.,,, <<< backtrace: |
Hello! After the last update (AIR 50.2.3.2) I’m getting a crash reports in Google Play console:
`*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
pid: 0, tid: 4993 >>> air.com… <<<
backtrace:
#00 pc 0x000000000086d7f4 /data/app/~~ORlO5qDH38ML3_mZGCKnFQ==/air.com…-rSoL_ATCOrEqJjs8f0nowA==/split_config.arm64_v8a.apk!libCore.so
#1 pc 0x000000000086d4e8 /data/app/~~ORlO5qDH38ML3_mZGCKnFQ==/air.com…-rSoL_ATCOrEqJjs8f0nowA==/split_config.arm64_v8a.apk!libCore.so
#2 pc 0x0000000000792f88 /data/app/~~ORlO5qDH38ML3_mZGCKnFQ==/air.com…-rSoL_ATCOrEqJjs8f0nowA==/split_config.arm64_v8a.apk!libCore.so
#3 pc 0x000000000074a174 /data/app/~~ORlO5qDH38ML3_mZGCKnFQ==/air.com…-rSoL_ATCOrEqJjs8f0nowA==/split_config.arm64_v8a.apk!libCore.so
#4 pc 0x000000000074d6d0 /data/app/~~ORlO5qDH38ML3_mZGCKnFQ==/air.com…-rSoL_ATCOrEqJjs8f0nowA==/split_config.arm64_v8a.apk!libCore.so
#5 pc 0x000000000000ebdc `
as I can see, it’s just Android’s problem, it occurs on different devices, so I can’t reproduce it by myself.
Also users reports about redirecting the app to the Google Play during the app launch (which is weird coz there is no redirecting functionality in the app). Thanks!
The text was updated successfully, but these errors were encountered: