Firebase Crashlytics setup on iOS?

firebase crashlytics not working ios
firebase crashlytics not working android
firebase crashlytics api key
firebase crashlytics github
cocoapods could not find compatible versions for pod "firebase/crashlytics"
firebase crashlytics flutter
firebase crashlytics react-native
migrate crashlytics to firebase ios

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:


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!

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, 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 initialisation 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.

Firebase Crashlytics, Step 7: Setup Crashlytics in Firebase console. Let's select NO for the step 1 (​Does this app already use Crashlytics?). If your app has the Fabric  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

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

Integrating Firebase and Crashlytics in iOS - The Startup, saves you troubleshooting time by intelligently grouping crashes and highlighting the circumstances that lead up to them. Firebase Crashlytics plat_ios plat_android plat_unity Get clear, actionable insight into app issues with this powerful crash reporting solution for iOS, Android, and Unity. Firebase Crashlytics is a lightweight, realtime crash reporter that helps you track, prioritize, and fix stability issues that erode your app quality.

I followed the 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

Firebase Android Series: Crashlytics, provides deep and actionable insights, even the exact line of code your app crashed on. Crashlytics - iOS Setup. A feature rich local notifications library for React Native by the team behind React Native Firebase. Additional iOS steps for

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

Android Fabric Crashlytics Integration, Choose 'No, set up a new Firebase app'. Now we need to install the SDK following these steps: Open the Build Settings tab in the Xcode project,  I’ve been writing this post using iOS 12.0 and the current Firebase SDK version is Firebase-6.3.0 Step 1: let’s create a new project in Firebase Console here . Just set the project name and

Crashlytics (legacy), Firebase Crashlytics is a realtime crash reporter t Getting Started with Firebase Crash Duration: 8:02 Posted: Jun 1, 2018 Open your Project Settings. In the Your apps card, select the bundle ID of the app for which you need a config file. Click Download GoogleService-Info.plist to obtain your Firebase iOS config file

How To Add Firebase Crashlytics To Your iOS App, iOS Dev : Setup Firebase Crashlytics in Xcode 10 - 2019. 3.8K views. 27. 7. Share. Save Duration: 9:02 Posted: Jun 21, 2019 select Go to Crashlytics docs on the screen like above. and then, a new tab is opened with Crashlytics installation. close the tab. you can see the screen below on Firebase Console. do the configuration below in this state. if you did the app setting first, do the configuration above and execute the app that is configured Crashlytics. after it

Firebase Crashlytics on iOS - Firecasts, 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, or you  Note: This guide contains instructions for the Firebase Crashlytics SDK, the official SDK for Crashlytics. You can find instructions for the Fabric SDK in the legacy guide . The Fabric SDK is now deprecated and will continue reporting your app's crashes until November 15, 2020.

iOS Dev : Setup Firebase Crashlytics in Xcode 10 - 2019, Step 1: Add Firebase to an iOS application; Step 2: Configure In the Crashlytics page of the Firebase console, click Set up Crashlytics. Step 2: Register your app with Firebase Go to the Firebase console. In the center of the project overview page, click the iOS icon ( plat_ios ) to launch the setup workflow. If you've Enter your app's bundle ID in the iOS bundle ID field. What's a bundle ID, and where do you find it? A bundle

  • The error message is clear, you have to get an API Key
  • That's what I thought, but the documentation clearly states that you do not need an API key. I finally found the solution, the on OSX automatically sets your Fabric api key in the app-info.plit file, which the script reads, and fails if you do not provide it with one. Removing this form the info.plist, and the script just plainly works.
  • I missed to add FirebaseApp.configure() in AppDelegate. After adding this, it worked perfectly.
  • 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 ?
  • 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 )`
  • 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.
  • Boom! This worked for me! Just trying to clean up my project in preparation for the full changeover in 2019
  • 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.
  • raplacing $(INFOPLIST_PATH) with GoogleService-Info.plist fixed it form