Development issue/problem:
I’m trying a new installation of Firebase/Crashlytics and I seem to have a strange problem.
I’m trying to submit a test according to Firebase’s instructions.
How can I solve this problem?
Solution 1:
Okay, I think I solved the problem, but the solution doesn’t seem to work as it should (at least, I don’t think so).
- Go to Firebase Console > Project Settings > Account Link > Fabric > Select Application and log out.
- Configure in Dust > App > Firebase – offline
- Go to Firebase > Project > Crashlytics (select the application you want) and you should now have a dialog box to link your application.
- Select the link as New Crashlitix (not available) and follow the instructions.
- After that, everything should be all right
So basically, from the Fabric>Firebase screen – no visible link, and from the Fabric>Link Counter>Firebase screen – no visible link either. So there is no link, but your failures will be visible in Firebase.
Solution 2:
It’s taking longer than I imagined to migrate well. Actually, you have two ways of doing it:
- Perform a clean migration without saving Fabric Crashlytics’ crash history.
This method is described in the Firebase Crashlytics Developer’s Guide. Here you need to remove the com.crashlytics.ApiKey metadata from the application manifest file.
Therefore, do not link Dust to Firebase, otherwise no errors will be displayed in the Firebase or the Dust console.
- Connect Fabric to Firebase and save your accident history.
This path is probably nowhere documented. The key here is to keep the com.crashlytics.ApiKey metadata in your manifest. Then you need to connect Fabric Crashlytics to Firebase. You can also activate the rebroadcast of events (previously Answers) in Firebase Analytics. Both actions are displayed in the Fabric console, search for Firebase in the side menu.
All new error messages are displayed in the Fabric console and the Firebase console. You can also use this link to copy the complete error history from Fabric to Firebase.
I don’t think the firebase artifact is needed here, but I added it. I also use Fabric events, so there are additional application usage events with Firebase-core in Firebase Analytics.
Solution 3:
I had the same question and it took me a long time to solve it.
I solved my problem by going to FireBase Console > [my project] > Crashlytics. Select your request from the drop-down list. Then the wizard appears with three steps.
Choose the option that suits you. I chose the first option because it is a new application. Then the second step appears.
And here’s the important part. Don’t forget to click on the link to access the documentation! A new browser tab opens. If you’ve already finished editing the project, like me, you can shut it down. You will then be automatically redirected to option 3. Usually I never clicked on the link because I had already completed the installation. And at one point, I didn’t even notice all three of them. The option was available because I was on a different tab. As a result, I have number three. Option never seen before.
At this point you need to open your application and it will automatically connect to Firebase without any problems.
Edit: After trying to add more compiler options, I noticed that I still got some errors when retrieving the settings. It took me a long time to find a solution to this problem. It’s the best I can think of:
- Possibility to continue construction
- Perform the assembly [YOUR_CONSTRUCTION_GUARANTEE] on the Notes tab.
- Construction project > Renovation
- Remove the old application from the device if it is present.
- install the application and open it.
Sometimes that didn’t work either, and I tried the same steps a few more times, and suddenly it started to work….
It also helped me to include an extra debugging input for the fabric and crash line.
adb shell setprop log.tag.Fabric DEBUG
adb shell setprop log.tag.CrashlyticsCore DEBUG
Solution 4:
If there is a network connection (e.g. in airplane mode), you will get this error even if everything is configured correctly.
You’ll get one too:
E/tissu﹕ Parameters of https://settings.crashlytics.com/spi/v2/platforms/android/apps/com.xyz/settings
not received W/tissu﹕ Zero parameters received, initialisation missed!
I do it to prevent further logging failures:
boolean fabricInitialized = Fabric.isInitialized();
if (fabricInitialized) {
Crashlytics.log(someString);
}
Solution No 5:
Go to the project settings and add the SHA-1 key for your Android application.
Then, reload google-service.json into your sources.
It makes this mistake to go away
E/Team: Settings cannot be retrieved from https://settings.crashlytics.com/spi/v2/platforms/android/apps/package.
And after a fairly long delay, you will see crashes in the Firebase console.
By the way, it doesn’t help me with applications that are stored in a Google Account and then moved to another one. I wish the Firebase team had acted on this.
Solution No 6:
You probably forgot to add something:
To your manifest file. At least in my case, that was the reason.
Solution No 7:
In my case,the location of meta-data:io.fabric.ApiKey was wrong.
- app/src/main/AndroidManifest.xml
à
à
I hope this helps.
Solution No 8:
I discovered that after switching to FirebaseCrashlytics, I had to unsubscribe and re-register my existing applications at Firebase.
Before you start the application, make sure you have gone to the following point for the first registration of FirebaseCrashlytics (the console is waiting for the first registration), otherwise the application will not be registered:
enter the description of the image here
This is not self-evident!
Solution No 9:
Upgrade to Firebase Crashlytics SDK Android and iOS
You can now customize Crashlytics in your application using the new official Firebase Crashlytics SDK, which offers improved APIs that are more compatible with other Firebase products and more intuitive to use. This tutorial describes how to switch from the Fabric Crashlytics SDK to the new SDK. It describes the changes that come with the new APIs, why they change, and how to update your code if necessary.
Android
Foreword : Migrate your application to AndroidX
1. Adding a Firebaseconfiguration file
- Open the project settings.
- Click Download google-services.json to download the Firebase Android configuration file.
- Move the configuration file to the module directory (application layer) of your application.
2. Switching dependencies
(project level)/build.gradle
Out of the question:
buildcript {
// …
deposits {
// …
// Delete Maven repository from Fabric.// // Delete Maven repository from Fabric.//
maven { url ‘https://maven.fabric.io/public’ }.
// Add the Google Maven repository (if it doesn’t already exist).
google()
}
Dependencies {
// …
// Add the Gradle plugin of Google Services (if not already present).
Classpath ‘com.google.gms:google-services:4.3.3’.
// Remove the plugin from the dust holder.
Classpath ‘io.fabric.tools:gradle:1.31.2’.
}
}
On:
buildcript {
// …
deposits {
// …
// Add the Google Maven repository (if it doesn’t already exist).
google()
}
Dependencies {
// …
// Add the Gradle plugin of Google Services (if not already present).
Classpath ‘com.google.gms:google-services:4.3.3’.
// Added Firebase Crashlytics Gradle plugin.
Classpath ‘com.google.firebase:firebase-crashlytics-gradle:2.1.0’
}
}
(app-level)/build.gradle
Finally, add the Firebase Crashlytics SDK. In your application-level build.gradle, replace the old Fabric Crashlytics SDK with the new Firebase Crashlytics SDK. For optimal performance with Firebase Crashlytics, we also recommend that you add the Firebase SDK for Google Analytics to your application (make sure you add version 17.2.3 or higher so that users don’t experience crashes and real-time breadcrumbs).
Out of the question:
Application plug-in: com.android.app
// Apply the Google Services plugin (if not already available).
Apply the plugin: com.google.gms.google services.
// Get the Fabric plugin.
Apply the plugin: io.cloth
Dependencies {
// Remove the Fabric Crashlytics SDK.
Implementation of com.crashlytics.sdk.android:crashlytics:2.10.1.
// Recommended : Add the Google Analytics SDK.
Implementing com.google.firebase:firebase analytics:17.4.1
}
On:
Application plug-in: com.android.app
// Apply the Google Services plugin (if not already available).
Apply the plugin: com.google.gms.google services.
// Add the Firebase Crashlytics plugin.
Apply the plugin: com.google.firebase.crashlytics.
Dependencies {
// Add Firebase Crashlytics SDK.
Implementation of com.google.firebase:firebase-crashlytics:17.0.0.
// Recommended : Add the Google Analytics SDK.
Implementing com.google.firebase:firebase analytics:17.4.1
}
Update of code
- Crashlytics.log is now a sample method.
Ex-works : Crashlytics.log (my message) ;
To the Firebase Crashlytics SDK:
FirebaseCrashlytics crashlytics = FirebaseCrashlytics.getInstance();
// Use the following syntax to record the crash message:
crashlytics.log(E/TAG: my message) ;
- Removing the crash method
Ex-works : Crashlytics.getInstance().crash().
To the Firebase Crashlytics SDK:
throw RuntimeException (test crash)
FirebaseCrashlytics now works automatically with the ContentProvider
as defined in the new Firebase Crashlytics SDK. Delete
calls to Fabric.with(), if applicable. If you are already using Firebase
Crashlytics, your application may already be using auto-run and
does not contain a call to Fabric.with().
GL
Solution No 10:
After checking the internet connection I solved the problem by enabling Crashlytics for my application in the Firebase console (then restart the application and everything should work fine).
Good luck!
Related Tags:
flutter crashlytics,firebase crashlytics android,fabric crashlytics,firebasecrashlytics: failed to retrieve settings from android,e/firebasecrashlytics: settings request failed. java.io.interruptedioexception: timeout,firebasecrashlytics: settings request failed java io interruptedioexception timeout,firebase crashlytics api key,firebase crashlytics not reporting crashes android,failed to retrieve settings from firebase crashlytics,firebasecrashlytics: create report http request failed,firebase console,crashlyticscore: received null settings, skipping report submission!
