Android Crashlytics problems

141 views

Skip to first unread message

unread,

Nov 20, 2018, 5:03:10 PM11/20/18

to Firebase Google Group

Hi,

I have an Android app in production which is successfully using the old Crashlytics dependency

com.crashlytics.sdk.android:crashlytics:2.8.0

I've been trying to release a new version of the app for days now using

com.crashlytics.sdk.android:crashlytics:2.9.5

and have had endless problems.

In particular I've found that :app:crashlyticsUploadDeobsRelease is not running in my new release

build. Also I'm now not seeing even obfuscated crashes in Crashlytics. The thing that does change

instantly on triggering a crash is that a new version name / version code appears immediately

in Filter > Versions in the window even though the crash doesn't show.

Does anyone have any insight into this? I've used the quickstart-android/crash sample successfully

but that's in debug not release mode. At one point I rolled the Android Gradle plugin back to 3.1.3

and reverted to my old settings of Crashlytics 2.9.5 and it suddenly worked again with no other code changes.

I guess that all the Fabric Crashlytics docs are relevant even though the official Android google docs

don't point at them afaics. Indeed, Google don't mention the Crashlytics log and I only found it from

Stack Overflow.

In my new version a lot of code is now written in a pure Java library. Fabric refer to this situation

It's not clear to me if I need to follow that as I'm not seeing crashes from pure Android eg in

Activity.onCreate

Any help very gratefully received!

Cheers,

Ewan

unread,

Nov 21, 2018, 8:13:20 PM11/21/18

to Firebase Google Group

I've created a Stack Overflow question for this:

Reply all

Reply to author

Forward

0 new messages