Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

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

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.

like image 683
Santhosh Avatar asked Jun 04 '20 14:06

Santhosh


People also ask

What is firebase settings Crashlytics com?

Firebase Crashlytics is a lightweight, realtime crash reporter that helps you track, prioritize, and fix stability issues that erode your app quality. Crashlytics saves you troubleshooting time by intelligently grouping crashes and highlighting the circumstances that lead up to them.


4 Answers

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.

like image 178
aaronvargas Avatar answered Oct 27 '22 05:10

aaronvargas


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://...:

enter image description here

like image 20
林果皞 Avatar answered Oct 27 '22 06:10

林果皞


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!

like image 4
the1900 Avatar answered Oct 27 '22 06:10

the1900


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.

like image 2
Kevin Kokomani Avatar answered Oct 27 '22 07:10

Kevin Kokomani