Geek Answers Handbook

Crashlytics non-deactivating code

I am new to Crashlytics and I have a problem when it does not remove obsolete stack traces. According to Crashlytics, this should happen automatically. It should use the mappings.txt file that is included in your .apk to decrypt the stack traces. I have a few questions about the whole process, as well as how I should solve the problem.

1) Should the mappings.txt file be packaged with the default .apk correctly? I use gradle; are there any parameters you should set?

2) I cannot load the stack from Crashlytics and not update the mappings.txt file in the toolbar. Are any of these options possible?

3) Can I get stacktraces elsewhere, the application has GSM services.

+8
deobfuscation proguard crashlytics
source share
1 answer

I had the same problem, but it seems to have been fixed by manually reinstalling the Crashlytics plugin.

Instructions at https://www.crashlytics.com/downloads/android-studio

(Using Android Studio 1.0 RC2)

EDIT: Crashlytics is now part of https://fabric.io
EDIT: Fabric is now part of https://firebase.google.com/docs/crashlytics/

+3
source share

More articles:


All Articles