crashlytics

问题 I tried new Firebase Crashlytics SDk after migrating from Fabric and seem to run into a weird issue. Crash logs are not captured in dashboard after upgrading firebase-crashlytics to 17.0.0 and I get this error in log: E/FirebaseCrashlytics: Failed to retrieve settings from https://firebase-settings.crashlytics.com/spi/v2/platforms/android/gmp/XXXX/settings and I followed all instructions from firebase console quickstart guide. Please help me if any one have faced similar issue. 回答1: In my

问题 I tried new Firebase Crashlytics SDk after migrating from Fabric and seem to run into a weird issue. Crash logs are not captured in dashboard after upgrading firebase-crashlytics to 17.0.0 and I get this error in log: E/FirebaseCrashlytics: Failed to retrieve settings from https://firebase-settings.crashlytics.com/spi/v2/platforms/android/gmp/XXXX/settings and I followed all instructions from firebase console quickstart guide. Please help me if any one have faced similar issue. 回答1: In my

问题 I tried new Firebase Crashlytics SDk after migrating from Fabric and seem to run into a weird issue. Crash logs are not captured in dashboard after upgrading firebase-crashlytics to 17.0.0 and I get this error in log: E/FirebaseCrashlytics: Failed to retrieve settings from https://firebase-settings.crashlytics.com/spi/v2/platforms/android/gmp/XXXX/settings and I followed all instructions from firebase console quickstart guide. Please help me if any one have faced similar issue. 回答1: In my

问题 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'm using React Native Firebase. At firebase crashlytics I have missing DSYM's. What's the right way to add dSYMs automatically on every build? I guess it should be added to run script? If so, how can I get the path to /path/to/pods/directory/FirebaseCrashlytics/upload-symbols and /path/to/dSYMs . Thanks! 回答1: This question has been answered in previous posts, but I'll provide a quick summary. The paths below will automatically find your dSYMs and upload them. Here is what goes into your

问题 I'm using React Native Firebase. At firebase crashlytics I have missing DSYM's. What's the right way to add dSYMs automatically on every build? I guess it should be added to run script? If so, how can I get the path to /path/to/pods/directory/FirebaseCrashlytics/upload-symbols and /path/to/dSYMs . Thanks! 回答1: This question has been answered in previous posts, but I'll provide a quick summary. The paths below will automatically find your dSYMs and upload them. Here is what goes into your

问题 I never setted crashlytics before and when i follow officials instructions https://firebase.google.com/docs/crashlytics/get-started?platform=ios&authuser=0#add-sdk i get stuck in the run script part crashlytics version 4.6.2 in the output i get a confirmation that crashlytics is setted but in the dashboard i see nothing 回答1: To test this you can force a crash.. What you can do is... Add a button on view and implement its touchupInside event. in that method just write fatalError() Run your app

问题 I never setted crashlytics before and when i follow officials instructions https://firebase.google.com/docs/crashlytics/get-started?platform=ios&authuser=0#add-sdk i get stuck in the run script part crashlytics version 4.6.2 in the output i get a confirmation that crashlytics is setted but in the dashboard i see nothing 回答1: To test this you can force a crash.. What you can do is... Add a button on view and implement its touchupInside event. in that method just write fatalError() Run your app

问题 In our project we were used the fabric for reporting crash, after that we have migrated the fabric with firebase and not removed the fabric due to the firebase was in beta. Right now we are trying to remove the fabric and crashlytics dependencies in the entire code: #pod 'Fabric', '1.10.2' #pod 'Crashlytics', '3.14.0' And used the below dependencies for Firebase Crashlytics.
 pod 'FirebaseCrashlytics', '4.5.0' pod 'FirebaseAnalytics', '6.8.0' pod 'FirebaseCore', '6.10.1' pod

问题 In our project we were used the fabric for reporting crash, after that we have migrated the fabric with firebase and not removed the fabric due to the firebase was in beta. Right now we are trying to remove the fabric and crashlytics dependencies in the entire code: #pod 'Fabric', '1.10.2' #pod 'Crashlytics', '3.14.0' And used the below dependencies for Firebase Crashlytics.
 pod 'FirebaseCrashlytics', '4.5.0' pod 'FirebaseAnalytics', '6.8.0' pod 'FirebaseCore', '6.10.1' pod