Solvedflutterfire π [firebase_crashlytics] Failed to retrieve settings from https://firebase-settings.crashlytics.com
βοΈAccepted Answer
May be it's a 24 hours patience game or try the solution below:
Few changes made were:
- Add
implementation 'com.google.firebase:firebase-analytics:17.5.0' implementation 'com.google.firebase:firebase-crashlytics:17.2.1'
to app level gradle- Add
classpath 'com.google.firebase:firebase-crashlytics-gradle:2.3.0'
to android level gradle.- Add
firebase_analytics
to pubspec.yaml, this is just a fluke.- Rebuild the app code and do a force crash in the app. And after waiting for a minute or two, upon refreshing Crashlytics Dashboard I see...
Thanks that work for me, but I need to call FirebaseCrashlytics.instance.crash();
to make Crushlytics console available.
I'm getting a Crushlytics alert in the console about migrate to the newer sdk
Other Answers:
Similar error:
E/FirebaseCrashlytics(17407): Failed to retrieve settings from https://firebase-settings.crashlytics.com/spi/v2/platforms/android/gmp/1:496886502013:android:fa533748f802011bf19714/settings
Someone has a solution to this:
Same problem here with 17.2.1, one of my app flavours didnt't work throwing above error. Removing current apps and re-adding them in firebase project settings solved the problem for me.
May be it's a 24 hours patience game or try the solution below:
Few changes made were:
- Add
implementation 'com.google.firebase:firebase-analytics:17.5.0' implementation 'com.google.firebase:firebase-crashlytics:17.2.1'
to app level gradle - Add
classpath 'com.google.firebase:firebase-crashlytics-gradle:2.3.0'
to android level gradle. - Add
firebase_analytics
to pubspec.yaml, this is just a fluke. - Rebuild the app code and do a force crash in the app. And after waiting for a minute or two, upon refreshing Crashlytics Dashboard I see...
Bug report
I added firebase_crashlytics to a new flutter app and ran it. In logs, it simply logs this error and my crashes are not reported to firebase console:
I hit this URL manually and it returns a 403 error. Not sure if it is expected or not.
Steps to reproduce
Steps to reproduce the behavior:
Expected behavior
The crashes should be logged in firebase upon next launch of app.
Additional context
I followed the tutorial here to add crashlytics: https://firebase.flutter.dev/docs/overview/
Flutter doctor
Click To Expand
Flutter dependencies
Click To Expand