CODEWITHSUNDEEP
androidcrashcrash-reportscrashlytics-androidfirebase-crash-reporting
Bolt UIX
Bolt UIX

Reputation: 7022

Strange Crash in CronetDynamite.apk (offset 0x1000) Android

My application had a crash report on Feb 1, 2021.

Crash LGE LG Premier Pro

Android 9 (SDK 28)

Playstore console crash have reported 40 times this report in CronetDynamite.apk

backtrace:

#00 pc 000000000018fb36 /data/user_de/0/com.google.android.gms/app_chimera/m/000001d4/CronetDynamite.apk (offset 0x1000)

Firebase Crashlytic does not show this crash... But Play console got this log

I didn't get what causes this crash, any help appreciated

Upvotes: 3

Views: 3261

Answers (3)

Mark
Mark

Reputation: 2562

I ran into this recently as well. Installed app works fine, no issues for users that have upgraded. It appears to be some issue with the Google Play Store's app testing system.

Upvotes: 4

Jiří
Jiří

Reputation: 251

The same error happened to me in Play Console tests, but only once. It was also accompanied by another piece of text: Native crash of com.google.android.gms. I do not use Google Mobile Services or Firebase. I only used libraries from a default Jetpack Compose application.

I think this means that it can be caused by Android OS and not by the application itself.

Upvotes: 1

JulianHarty
JulianHarty

Reputation: 3286

I don't know the cause of the crash, however cronet is provided by Google, who describe it as:

Cronet is the Chromium network stack made available to Android apps as a library. Cronet takes advantage of multiple technologies that reduce the latency and increase the throughput of the network requests that your app needs to work.

https://developer.android.com/guide/topics/connectivity/cronet

My guess is they've got some unusual crash related to their library which is being used in your app somehow (perhaps even in the Firebase Crash Reporting SDK implementation?).

As you reported this crash 6 months ago I hope you've found a workaround or fix. Please do add an update here.

If you're still suffering from the issue, try raising a bug report with Google. The same web page says:

You can send feedback about the Cronet Library using the Chromium Issue Tracker. Check the list of bugs in the issue tracker to make sure that your issue hasn't already been reported. If your issue hasn't been reported, file a bug with the word Cronet in the summary line.

All the best

Upvotes: 0

Related Questions