E/FirebaseCrashlytics: Failed to retrieve settings from https://firebase-settings.crashlytics.com/spi/v2/platforms/android/gmp/XXXX/settings

Question

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.

Solution 1

In my case, I had migrated the release version but I guess I never enabled Crashlytics on the Firebase console for the debug variant.

A simple mistake, but putting it here in case it helps out someone else.

Solution 2

If you enabled multiple apps in single project, ensure you choose the correct one (left drop down menu choose the correct project which hold the multiple apps, right drop down menu choose the correct running app). I made such mistake and keep looking on the wrong app page and enabling Crashlytics on the wrong app and of course I get that error "Failed to retrieve settings from https://...:

Solution 3

In my case, There was a legacy firebase project which using same package name of app. When I deleted legacy firebase project and It's works like a charm!

Solution 4

Firebaser here -

We often see these kinds of errors after upgrading due to some sort of configuration error when you were switching out your dependencies. Did you make sure to follow all the steps in this guide?

You may also want to enable Crashlytics debug logging and force a test crash to see if the logs give you any other output. And it may help to edit your original question with your Gradle files and any other relevant Crashlytics setup.

View more solutions

Comments

[Santhosh]

luckly for my case, the issue was fixed after updating to firebase-crashlytics 17.0.1

[Néstor]

@Santhosh my case is the oppose to you: just after update to 17.0.1 I got this error.

[Kevin Kokomani]

Would you be able to post a full log file? Or reach out to Firebase support with it if you don't want to post it here? Sounds strange. Debug mode would output more info as well, so try enabling that: firebase.google.com/docs/crashlytics/…

[Ryan R]

Yup had to click Enable in the FB console. Thanks!

[Hilal]

How do we enable it from console? Could you please give more information about it? Thanks in advance

[Anatol Bivol]

@Hilal go to Firebase Console > Crashalytics > Click Enable > Wait 5-10min

[Mahdi Javaheri]

This worked for me. must be accepted answer

[prsnlme]

You saved my day

[Chris]

Can't believe I didn't notice that!