Firebase integration with my app is working like a charm.
So I tried to add Crashlytics.
After pod the SDK and configuring my app in XCode, I've got the version message on log:
"2020-10-23 14:13:36.386002-0300 Findn[44158:3074710] [Firebase/Crashlytics] Version 4.6.2"
But at Firebase Console there isn't a card for Crashlytics.
And at Crashlytics tab this circle keep spinning.
Any tips?
EDIT:
Guess I wasn't clear enough, sorry.
I did follow all guidelines to integrate Firebase to my app.
The problem seems to be on Firebase side, since my app's log does not report any errors on xcode.
Yes, Now you can not use fabric solely. You have to integrate firebase to use a fabric.
Check this link:
firebase crashlytics
Maybe the solution is here!
The steps are the following:
Ensure you add the code in order to force a crash, something like that firebase
First, you need to build the app and launch the app with Xcode,
Next launch without attaching with Xcode (manually, tapping on icon app), and force crash app with fatalError()
Then launch with Xcode and the app will send the traces... đź’Ą
Related
I have run my app on a device and in simulator with no success of updating the Firebase Crashlytics system.
I am not getting any errors, and I know that it's installed because it says the version number (4.5.0) in console.
Also Firebase Analytics is working.
I have followed the install guide to a T and also tried to force crash it by creating a SwiftUI button and using
fatalError()
Which seems to not fully crash the app, but more freeze the app.
I am wondering how I can trace this issue with SwiftUI and Firebase.
In addition of doing what the accepted answer recommends and I believe this is something new from Xcode 12.+. You need to uncheck the two checkboxes below the script window (at least once - you may tick them back up once registered with firebase). This (as stated) forces the script to run and therefore to communicate with firebase... the checkboxes unticked
As outlined here, if you're going to use the Xcode Simulator, you must detach the Xcode debugger at runtime by launching the app directly from the Simulator and not Xcode. Xcode automatically attaches its debugger if you launch from Xcode to a Simulator, blocking Crashlytics from being able to see exceptions/crashes.
I have implemented Firebase Analytics 6.15.2 into my project, then I have builded the Xcode project and have run it on the device, everything went perfect, but when I try to open the app afterwards, without it running from Xcode - it crashes after 20 seconds of launch screen.
So I have no logs and anything, I somehow figured out it's an issue with Firebase and downgraded the pods in the Xcode project to Firebase 5.3.0, it worked.
I have other projects where the same issue is occurring.
So my question is, how do I fix it? Because there is no way it's happening to everyone, I might be doing something wrog here and I just don't see it.
I use Unity 2020.1.2f1
Firebase Core + Analytics 6.15.2 via Package Manager (also tried installing it manually, still the same)
Other plugins I am using are Facebook and ironSource
ps. The funny thing that it crashes on all devices, but it passes Apple review because they test it in some kind of debug mode, but when it's in release mode - it crashes.
Have you tried to reinstall Firebase Analytics 6.15.2? Also, you can try to restart your device and try to make it work again.
You need to add the debug symbols to your app debug archive file:
Select your Target -> Build Settings -> Build Options -> Debug
Information Format
Then Select DWARF with dSYM file for the debug mode.
https://firebase.google.com/docs/crashlytics/get-started?authuser=2
I followed this link and the Firebase Analytics connected and showed events, but Firebase Crashlytics is not showing any crash, it isn't even able to connect to App.
And keeps showing the following image when clicked on Crashlytics in Left panel from Firebase Console.
This is a fresh project Firebase Crashlytics works fine with the earlier projects created using Fabric.
I resolved this issue by Adding Run Script as shown in Firebase, also I did a fresh start.
https://firebase.google.com/docs/crashlytics/get-started
For some reason, following the Firebase docs did not work for me as I had to do a few additional things for the "Add the SDK" loading screen to disappear on the Firebase portal and show me the crashes.
In addition to what the Firebase docs say, I did the following in addition to this answer which I have also outlined on a similar issue here
Go to Build Settings -> Debug Information Format -> Set all of them to DWARF with dSYM file
Go to Build Phases -> Add an additional run script and input the following
${PODS_ROOT}/FirebaseCrashlytics/upload-symbols -gsp ${PROJECT_DIR}/Your_path/GoogleService-Info.plist -p ios ${DWARF_DSYM_FOLDER_PATH}/${DWARF_DSYM_FILE_NAME}
Remember to replace {PROJECT_DIR} appropriately for your project
Stage a crash in your application as described here
Disconnect your device / simulator from the debugger AKA launch it on your own rather than running it from XCode and then perform the crash
I was now able to see the above loading disappear and I could see my crash statistics instead
I've just recently installed Fabric to a project which already had Firebase installed and suddenly Crashyltics has stopped working. It's not included within the 'Fabric.with([])' call on AppDelegate.swift but I wondered if Fabric and Firebase were cancelling out Crashyltics. I'm using Fabric for it's Beta option and everything else is inside Firebase.
I can force a crash inside the app - But not getting anything reported in either Dashboard.
My run Script Phase is also correct.
My Debug is DWARF with DYSIM.
Cleared derived data etc.
Firebase is called after Fabric inside AppDelegate.
Thanks
I think that you have to link your firebase and fabric apps.
Go to https://fabric.io/firebase_migration/status, click on link apps and select the apps to link (the one on fabric and the corresponding app on firebase)
Do you upload your dSYM to Firebase/Crashlytics? If not it can be the issue.
I'm upgrading from Fabric to Firebase crashlytics. I've added Firebase and Fabric/Crashlytics pods to my project, added the .plist etc. All seems to be working fine, except crashes are not being reported. I'm generating a crash using assert(! "crashing on purpose to test crashlytics"); as I saw someone else mention [[Crashlytics sharedInstance] crash] didn't work for them.
What's interesting is the 'crash free users' for the build number I'm using drops to 0% after the crash is generated, but crashes is reported as 0. The dSYMs tab doesn't list the version number.
Here's the crash coming through on the debug view when -FIRDebugEnabled is passed as an argument:
Any suggestions?
I had a similar issue when migrating from Fabric to Firebase Crashlytics. You should not follow the Firebase website instructions. Stick with the Fabric instructions as mentioned by #Ashvini. I am assuming that you already had Crashlytics working fine before migration to Firebase. I tested this approach and it works for me.
This is a pain as older and newer projects will have different Crashlytics implementations.
After installation make sure you have initialized Fabric SDK in your AppDelegate file by using below line of code:
For Objective-C : [Fabric with:#[[Crashlytics class]]]; and
For swift : Fabric.with([Crashlytics.self])
After that force your app to be crash by calling Crashlytics.sharedInstance().crash() for swift and [[Crashlytics sharedInstance] crash] for Objective-C. Call this method by adding any button programmatically in your ViewController or on existing action.
Crashlytics doesn’t capture crashes if a debugger is attached at launch, so to see the crash in action you'll need to follow these steps:
Run your app from Xcode to install it on the simulator or your device
Press the Stop button in Xcode to quit it
Launch your app from the home screen to run it without the debugger
Press the “Crash” button to trigger the crash
Run the app again from Xcode so it can deliver the recorded crash to Crashlytics.
Within a few minutes, you should see the crash appear on your Fabric Dashboard.
If you didn't found crash in dashboard then Double-check in your Build Settings that your Debug Information Format is “DWARF with dSYM File” for both Debug and Release.
Make sure to launch the app after crashing it, so that the crash can be uploaded.
If you don’t see the crash after a few minutes, run your app again to retry crash delivery.
You can refer to this link [https://fabric.io/kits/ios/crashlytics/install] .
See that you have the latest pods installed, as the firebase docs says you should have this pod versions
pod 'Fabric', '~> 1.9.0'
pod 'Crashlytics', '~> 3.12.0'
Here is the link to the docs of firebase crashlitycs