33

I recently changed targedtSdk to 29 and made a release. And started getting this crash called abort. Below is the stack trace that I got from play console. All the crashes are happening only in Android 10 devices. Apart from these, there is no other info.

   #00  pc 0000000000082fb4  /apex/com.android.runtime/lib64/bionic/libc.so (abort+160)
   #00  pc 00000000004b4888  /apex/com.android.runtime/lib64/libart.so (art::Runtime::Abort(char const*)+2268)
   #00  pc 000000000000c5b4  /system/lib64/libbase.so (android::base::LogMessage::~LogMessage()+608)
   #00  pc 0000000000442f8c  /apex/com.android.runtime/lib64/libart.so (art::OatHeader::GetCompilerFilter() const+280)
   #00  pc 000000000044a884  /apex/com.android.runtime/lib64/libart.so (art::OatFile::GetCompilerFilter() const+40)
   #00  pc 0000000000455d38  /apex/com.android.runtime/lib64/libart.so (art::OatFileManager::DumpForSigQuit(std::__1::basic_ostream<char, std::__1::char_traits<char>>&)+376)
   #00  pc 00000000004c1d78  /apex/com.android.runtime/lib64/libart.so (art::Runtime::DumpForSigQuit(std::__1::basic_ostream<char, std::__1::char_traits<char>>&)+104)
   #00  pc 00000000004d5ad8  /apex/com.android.runtime/lib64/libart.so (art::SignalCatcher::HandleSigQuit()+1356)
   #00  pc 00000000004d4b6c  /apex/com.android.runtime/lib64/libart.so (art::SignalCatcher::Run(void*)+252)
   #00  pc 00000000000e205c  /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+36)
   #00  pc 0000000000084af0  /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64)```


Made a staged rollout of 50% and the number of crashes for above is around 800 per day with active installs of 1.5M. So this is a major issue.
Improve this question
11
  • ?stackoverflow.com/questions/61321845/… Commented Jul 23, 2020 at 5:42
  • We found that the issue was because of upgrading facebook sdk to the latest version, we reverted to the older version and made a release, the issue didn't occur. Following it up with facebook now. Not sure if this is the reason for others as well. Commented Sep 13, 2020 at 14:13
  • @Velu,We've faced the same crashes as you, can you share what facebook sdk did you use and the versions of the sdk? Commented Sep 14, 2020 at 3:57
  • @notTdar It is not the same issue. Hi Velu, Could you please share with me the Facebook version? also, my app report only on Oppo devices Commented Sep 16, 2020 at 6:12
  • 1
    Hi @Velu, very appreciate with your guideline, I will take a look on my app. This is helpful. Thank you Commented Sep 23, 2020 at 8:15

4 Answers 4

Reset to default
3

I did not use com.facebook.android:audience-network-sdk, and have been trying to fix this for a week now. After much research on the web (and finding nothing of use), I decided to bet it was some sort of incompatibility between some lib and the Andriod version. Took the libs out one by one, and found that, in my case at least, the problem was Sentry. Simply not invoking it during app start solved the issue.

Improve this answer
Sign up to request clarification or add additional context in comments.

2 Comments

Do you know why Sentry causes this error? I want to use it, but anytime i get a null ref it crashes
@MarionPiloo never found out. Moved on without sentry and eventually switched it for another similar lib
2

I fixed this bug， from implementation 'com.facebook.android:audience-network-sdk:5.11.0' to implementation 'com.facebook.android:audience-network-sdk:5.4.1'

But can't find the reason

Improve this answer

7 Comments

Hi @yukun, this is not the same issue from Velu has post, but your answer already help me ;-). So if you make your comment on your question is answer, I will vote for it ;-)
I have the same crash log.I think it's the same one
stackoverflow.com/questions/64007059/…
Hi @yukun, I means you have same crash log as Velu, however, Velu downgrade the com.google.ads.mediation:facebook, in your case, it is com.facebook.android:audience-network-sdk. So same crash log, but difference aar to make app crash
com.google.ads.mediation:facebook dependence on com.facebook.android:audience-network-sdk.
|
1

As per https://issuetracker.google.com/issues/148240970#comment8 it looks like something to be fixed for Android 11 onwards, without a known fix for Android 10.

Improve this answer

Comments

1

enter image description hereAudience Network SDK 6.2.0 seems to solve the problem

https://developers.facebook.com/docs/audience-network/changelog-android#6_2_0

Improve this answer

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.