Firebase Crashlytics setup on iOS?

Question

I'm trying to integrate Firebase Crashlytics into iOS my app, which has Firebase Crash Reporting enabled. I've followed the documentation here, but my build always fails when running the custom build phase:

"${PODS_ROOT}/Fabric/run"

The error in Xcode is the following:

error: Fabric: Configuration Issue

Fabric API key not valid. Your Fabric run script build phase should contain your API key: ./Fabric.framework/run INSERT_YOUR_API_KEY INSERT_YOUR_BUILD_SECRET

I do not have a Fabric API key and I suppose that they fabric keys should be taken care by the Firebase library. I have the Info.plist in my project, Firebase is fully functional, but I cannot get past the Fabric run phase. Any help on how to fix this is greatly appreciated!

Solution 1

Finally figured it out, posting for anyone that might be baffled by the same problem.

If you've tried to install fabric via the OSX Fabric.app, or you were using Fabric Crashlytics in the past, then it will have added your Fabric API key to your Info.plist, which the Fabric initialization build script is trying to read (I guess).

After deleting the Fabric keys form the Info.plist the script works, without the need of any keys/params.

The Firebase docs should include a snippet warning on this.

Solution 2

If you follow closely the Getting Started documentation, you might be in for some frustrations. Trust me. I had my share of that.

Now here's what I can share with you.

1. If you previously had Fabric RunScript for that Target, then it's best if you delete that and create a new one, apply the GettingStarted instruction, and replace the $(INFOPLIST_PATH) with GoogleService-Info.plist.

2. There should be no Fabric configuration on your Info.plist file anymore. It's this thing: <key>Fabric</key><dict>...</dict>. If you still have that, time to say goodbye and let go of those feelings or face this issue.

3. If you keep seeing this in your Xcode console, [Fabric] failed to download settings Error Domain=FABNetworkError Code=-5... blah blah blah, then go clean that Build Folder first (shift + cmd + k).

If your next build works, try force crashing your app and check out the crash logs on Firebase.

Here's my stack: Xcode 10.2.1 | Fabric 1.9 | Crashlytics 3.12

Solution 3

The issue for me was I was using the old Fabric before and I had to remove the key from my info.plist

Solution 4

I followed the https://fabric.io/kits/ios/crashlytics/install documentation and added the Run Script and updated Info.plist but still got the above issue.

Apparently, I had accidentally added twice 'New Run Script Phase'. After removing the unnecessary 'Run Script's the project compiled successfully.

Xcode 10.1 Fabric 1.7.5 Crashlytics 3.10.4

Solution 5

Documentation

• if crashlytics is already set up in your project (in case of migration),

  1. Remove the fabric key from Info.plist (need to remove the dictionary and the key for Fabric)
  2. Follow the documentation.(just need to use "${PODS_ROOT}/Fabric/run", instead of "${PODS_ROOT}/Fabric/run" key1 key2 in the Run script under build phase)

• if crashlytics is not setup in your project already(starting a fresh integration with firebase crashlytics), simply follow the documentation.

View more solutions

Comments

[Illep]

I had the exact same issue, and I followed your post and removed the API key. It works now. But, the Crashes are not logged on Firebase. Any Idea why it takes place ?

[Lucas P.]

I had some issues as well using Crashlytics.sharedInstance().crash() (on Android though, it worked on iOS) so I would suggest creating an actual crash like this: let nilVar: String? = nil nilVar!.isEmpty() Let me know if the crash appears then (give it at least 5 minutes, although when it works crashes appear almost instantly).

[Illep]

Sadly no. It doesn't get recorded in firebase. But it says that the crash has been uploaded . ` <Notice>: [Firebase/Crash][I-CRA100002] Crashes uploaded successfully: ( 1e21a90b1c000000 )`

[Lucas P.]

Are you other firebase services working (have you verified that your app is set up correctly)? Do you also have Firebase Crash Reporting enabled? You should remove the FirebaseCrash pod, since only one crash reporting library can be active at a time on iOS.

[Illep]

In the console for Users active in last 30 minutes it says 1 user, so i guess firebase has been configured correctly. What do you mean by Firebase Crash Reporting enabled ? I have it setup from console, but see no reports in it. Why should I remove FirebaseCrash pod ? the doc says to install it

[Lucas P.]

The Crashlytics docs here states that when migrating from "Firebase Crash Reporting" to "Firebase Crashlytics" that you have to remove the "Firebase Crash Reporting" library. (for the reason I mentioned above). Try it and let me know.

[atodTechies]

For my project, had to unlink Fabric from Crashlytics and had to do all of the above in order for the crash logs to appear in the Firebase Dashboard. This seems to be an issue for iOS only.

[Gurjinder Singh]

I have remove the keys from plist and also added the required script. But still showing the same error for key.

[Christian Gossain]

Boom! This worked for me! Just trying to clean up my project in preparation for the full changeover in 2019

[NightWatcher]

Hi All, I am migrating an iOS application from Fabric to Firebase and facing a similar issue. My question is "Do we need to delete Fabric Initialization(from AppDelegate) and Fabric Key(from Info.plist) or not?" If we delete it then Firebase is not getting the crashes. If we don't delete it then why do we need to add Firebase to the App? I mean by linking the app to Firebase we will get all the crashes.

[Raiss]

raplacing $(INFOPLIST_PATH) with GoogleService-Info.plist fixed it form

[ytpm]

I had a true belief that his should work, but no it didn't..