I am trying to switch from Firebase Crash reporting to Firebase Crashlytics.
I have followed the guide here:
https://firebase.google.com/docs/crashlytics/upgrade-from-crash-reporting
But during initialization the logs says:
Received null settings, skipping report submission!
And then when testing crashes:
Cannot send reports. Settings are unavailable.
Network connection is good, so no reason why it can't get settings.
Log output:
D/CrashlyticsCore: Initialization marker file created.
W/CrashlyticsCore: Received null settings, skipping report submission!
D/CrashlyticsCore: Initialization marker file removed: true
D/CrashlyticsCore: Crashlytics is handling uncaught exception "java.lang.RuntimeException: Testing crash" from thread main
D/CrashlyticsCore: Logging Crashlytics event to Firebase
D/CrashlyticsCore: No log data to include with this event.
D/CrashlyticsCore: Unable to close session. Settings are not loaded.
D/CrashlyticsCore: Opening a new session with ID 5A042DD20217-0002-4F33-A5AF620D03D1
D/Fabric: Falling back to Crashlytics key lookup from Manifest
D/Fabric: Falling back to Crashlytics key lookup from Strings
D/Fabric: Falling back to Crashlytics key lookup from Manifest
D/Fabric: Falling back to Crashlytics key lookup from Strings
W/CrashlyticsCore: Cannot send reports. Settings are unavailable.
D/CrashlyticsCore: Crashlytics completed exception processing. Invoking default exception handler.
You need to link your project to Fabric. Ignore it if you already did it. Else follow these steps
It will navigate to Fabric and follow the instructions (create an account or sign in if you already have an account). After successfully logged in to the Fabric, Next you have to link your project to Fabric for that you can use the Fabric plugin.
After installing the plugin you can open it by clicking either of the below options shown below.
And follow instructions to create the Fabric project.After that from the firebase console -> Crashlytics -> link your firebase project to Fabric project.
That's all...
When upgrading from Fabric Crashlytics to Firebase Crashlytics I found that I needed to make sure that AndroidManifest.xml contained this attribute from Fabric. After having correctly linked the App in Fabric with Firebase. Which you can find at https://www.fabric.io/settings/organizations,
<meta-data
android:name="io.fabric.ApiKey"
android:value="..." />
(Replacing ... with your key)
This needs to be within the <application> block. Once I included this the settings were detected and crashes appeared in the Firebase console, email alerts.
In my case this same error occurred because i already had forced the crash on the device as required by setup tutorial, for a different flavor of the application.
My App has 2 flavors, so in order to successfully link flavor number 2 i had to force crash on a different simulator.
Note: The 2 flavors need to have different packages at least.
Same happened to me. I had another flavor of the app installed, so I deleted all flavors currently installed and it worked after simulating the crash again.
Related
I have setup firebase in my react native app.
But currently exceptions are not handled means not added any crashlytics logs or recorded errors
But for android app I am getting crashes in firebase but not for IOS.
Can someone explain this in detail?
Crashlytics may only be able to upload the data once the app starts again. Did you restart the app?
This can happen if you are testing while the Xcode debugger is attached.
Check this document, it explains how to test this in iOS.
If that doesn't work, enable debug logging and check if something is causing issues. For this:
After enabling debug mode, run the app.
Then hit "stop" in Xcode.
Run the app in the device and crash it
Run the app again from Xcode
Collect the output from Xcode
I am having problems running my application all of a sudden.
The error are shown in the screenshot. I have no idea what has happened. What do the errors mean?
enter image description here
App targets Android 12 or higher and contains activities, services, or broadcast receivers that use intent filters. Please explicitly declare the android: exported attribute for these app components.
Also this is applicable to all the activities, services, broadcast receivers that use an intent-filter. After making the changes. Save it , Invalidate cache and restart android studio and check
I have carefully followed the instruction from fabric (https://fabric.io/kits/ios/crashlytics/manual-install) to install crashlytics in my app. However I cannot select my app after the instruction since my app is not showing. I have tried most of the solution that has been given in this question here (Crashlytics in iOS won't proceed past "Build Your Project" in Fabric app)
But I still failed to get my app in fabric.
I am using react native to develop my app and using Xcode Version 10.2.1
Fabric/Firebaser here - If you've gone through all the necessary instructions, try cleaning your project first before building and running again to try to get your app up on your dashboard. And if you haven't seen it, here are some instructions specifically for setting up react native apps with Crashlytics: https://www.npmjs.com/package/react-native-fabric#crashlytics-usage). And make sure that if you haven't, set the Debug Information Format to DWARF with dSYM file for both debug and release as specified in that SO post you linked.
You can also see more debug information about Fabric if you set Fabric to debug mode in your initialization statement: https://docs.fabric.io/apple/fabric/advanced-settings/debugging.html. Check to see if the settings requests are being made to Fabric or if there is anything unusual.
If you're still having trouble, reach out to support(at)fabric(dot)io with your app's bundle ID and support will be able to help you out more.
For some reason we needed to change the package-id of our existing android application. We already use Fabric for Crashlytics.
I'm trying to bring that new app up in the Fabric dashboard, but it's not showing there, despite the device log showing no issues (as fas as I can see): device log
Any ideas why the new package-id isn't visible in our dashboard?
Best,
Sven
I experienced a very similar issue to this when building an app with multiple flavours. The solution is to manually specify the package name, and not let Fabric try to automatically grab it, as it tries very hard to "stick" your old package name.
There is a full post available (disclaimer: my site), but essentially you need to use:
Fabric.with(
Fabric.Builder(this)
.kits(Crashlytics())
.appIdentifier(BuildConfig.APPLICATION_ID)
.build()
)
Make sure to include all dependencies on their dedicated gradle.build and meta in manifest file. Next is to throw a force runtime error on your device with internet connection also do not forget to initialize it first with Fabric.with(this,new Crashlytics()). If this doesn't work try to download and install Fabric for Android plugin in Android Studio, restart the IDE and you will see a fabric icon above. Start it and select your package name.
I had the exact same problem, in the log I clearly see that the Crashlytics is in use.
I/CrashlyticsCore: Crashlytics report upload complete: <ID>
But I cannot see my project on the dashboard, and always redirect to the tutorial.
After a Build-Clean and an Android studio restart, build and run the app again to my phone, and voilá, it finds itself. Now working, without any change.
I have the same problem. After hours of researches I resolve this for my application.
First: After adding new flavour, I make changes in Firebase console (added new app in existing project, with production SHA1, changed google-services.json).
After that app does not show in fabric dashboard and fabric plugin in Android Studio. Problem was resolved after linking new app in crashlitycs in firebase console. And after that check your roles, must have Owner role (on Firebase Console Project).
Downloading beta app from testflight app gives error at the end, says "Unable to download app at this time" on all my devices.
No error is in itune connect upload. App displayed and received notification on adding new app to testflight beta. But everytime same error.
This happened to me when I wasn't using the correct provisioning profile. Very frustrating error that doesn't provide any useful info, and leaves the previous installed version of your test build in a state where it cannot be launched. After I switched my provisioning profile to 'Automatic', bumped the build number, and submitted a new version to iTunes connect I was able to download the new build.
I'm seeing a similar error. I don't know for sure, but I suspect doing things in this order may have something to do with it (this seems to mirror what emrys57 is facing).
You have issued a previous TestFlight release (download/install was working).
You then submitted that version for formal review for publication in the App Store.
While the app submission is still under review, now you uploaded a new TestFlight build with an updated version number (but did not resubmit for App Store review).
It could be that while the app is under review something prevents the download. I seem to recall reading about something like this in one of the guides, but I can't remember where off the top of my head. In my case, as an internal tester I even face the error "Unable to download app at this time", regardless of whether I already have a previous version with the same bundle ID already installed or if I don't have the app already installed (i.e., it's fully uninstalled). I wonder if an accepted App Store review will clear up the issue; it doesn't seem like a good idea to resubmit that latest build for further App Store review if the version previously submitted is what you actually want released.
In my case, for the general testing audience, I have a separate bundle ID that is exclusively for beta testing. And that version is never submitted for App Store review (the one that's slated for App Store review I only use for the purpose of smoketesting the upgrade process with internal testers). That bundle ID for beta had to go through the one-time full TestFlight external review for the initial TestFlight external beta testing. But I've been able to keep adding new versions to that beta-only bundle ID for subsequent TestFlight releases without an issue.