crashlytics-android

问题 I recently publish my app to play store as a app bundle and everything is working fine except for above mentioned issue. I have added bellow pro-guard rules in my app and it was working fine with my old builds. #CrashLitics -keepattributes SourceFile,LineNumberTable -keep public class * extends java.lang.Exception Is there any addition pro-guard rules to include when publishing as a app bundle? 回答1: I contacted the Firebase team. Their reply was to add :app:crashlyticsUploadDeobsRelease (or

问题 Crashlytics allows strings to be sent with crash logs, but how can they be unset? Let's say I working on a media player. Sometimes I want to send a non fatal log with a media id. Other times I want to send a log without a media id. 回答1: You just need to pass null as a value in the arguments String key = "mediaId"; Crashlytics.setString(key, null); There is check inside this method if value is null then it will set empty string: public void setString(String key, String value) { // some code

问题 Is it possible on android to programmatically initialize firebase-crashlytics SDK so it would not use the data in google-services.json ? I am asking this because we use two firebase projects and currently google-services.json is of the project we use for Push notifications and AdMob integration, and I cannot replace it with google-services.json of the second project we have set up for crashlytics. I have already tried using FirebaseOptions from my Application onCreate as follows:

问题 I recently upgraded my app to Firebase Crashlytics SDK following this guide (https://firebase.google.com/docs/crashlytics/upgrade-sdk?platform=android) . I tested it and it worked properly so I uploaded it to Google Play. The problem is that I am receiving many error reports from my users since then. The report is as follows: java.util.concurrent.RejectedExecutionException: at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution (ThreadPoolExecutor.java:2086) at java.util

问题 I use crashlytics to send my reports but crashs not de-obfuscated like this: Fatal Exception: c.a I readed here and added -keepattributes *Annotation* -keepattributes SourceFile,LineNumberTable to my proguard-rules file and there is no -printmapping mapping.txt in my configuration files. this is my build.gradle buildTypes part: buildTypes { release { minifyEnabled true shrinkResources true proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro' } debug_server {

问题 I use crashlytics to send my reports but crashs not de-obfuscated like this: Fatal Exception: c.a I readed here and added -keepattributes *Annotation* -keepattributes SourceFile,LineNumberTable to my proguard-rules file and there is no -printmapping mapping.txt in my configuration files. this is my build.gradle buildTypes part: buildTypes { release { minifyEnabled true shrinkResources true proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro' } debug_server {

问题 I want to send info about user non-fatal exceptions through recordException() method, but default crashlytics implementation sends them only after app is restarted (which is quite a strange behaviour o_O) I tried to disable automatic reports collection through setCrashlyticsCollectionEnabled(false) method and send them manually through sendUnsentReports(), but, alas, firebase continues to send them only after the app is restarted. Has anybody solved that kind of a problem and how? 回答1: Yes,

问题 I've been testing Firebase Crashlytics and even though the normal crash report works right I can't success trying to generate a custom as it says the documentation. Crashlytics.log(msg); I also would like to know wether setting the user identifier for Crashlytics can be done for any crash (according to the doc I've understood that it's possible) with void Crashlytics.setUserIdentifier(String identifier); and how it would have to be done, because it does neither work to me, I can't see

问题 I have been using firebase for android for 1 year now. For last few days i have noticed that firebase crashlytics on console not showing event logs as they were shown previously like this It see all the screens the user went through right before a crash happened. It was really helpful. Now it is not showing in console. No sub tabs are visible in log tab. Does firebase remove the feature ? or i am missing some property to enable to make it visible on console. 来源： https://stackoverflow.com

问题 I have been using firebase for android for 1 year now. For last few days i have noticed that firebase crashlytics on console not showing event logs as they were shown previously like this It see all the screens the user went through right before a crash happened. It was really helpful. Now it is not showing in console. No sub tabs are visible in log tab. Does firebase remove the feature ? or i am missing some property to enable to make it visible on console. 来源： https://stackoverflow.com