Crashlytics in iOS won't proceed past “Build Your Project” in Fabric app

Question

I\'m installing Crashlytics for my iOS app. I downloaded it via their site link, and went through all the steps for integrating the frameworks, adding the run script, etc. <

Answer 1

What I did wrong was adding the script to the pods project build phase instead of the main project build phase, adding it to the main projects build phase solved the problem.

Answer 2

TL;DR

Tap your scheme -> edit scheme -> set build configuration to "Release"

Explanation:

The most voted answer sounds about right, but there are situations where you just don't need crashlytics in debug builds (who wants crashes sent when you just develop and experiment with your code?). In this case you should disable crashlytics by checking debug compilation flags (out of scope of this answer) and for the first time during installation build app for release to let crashlytics know that you built app.

Answer 3

Nothing helped me. Now Fabric catches my archive creation. But I create the archives via fastlane's build_app.

Answer 4

In my case, removing an app from helped. 1) Remove the app from Fabric. 2) Follow all the steps again to add the app and install Crashlytics.

Answer 5

Moving from Comment to Answer.

Mike from Fabric here. If you back up through the Mac app, then click on the arrow in the top-left, click on "+ New App", that will walk you through re-adding everything.

Answer 6

None of the solutions here worked for me. The scenario for me was someone else added the Fabric framework to our project and committed it to the repo. The run script on their computer launched/triggered the Fabric Plugin, but would not launch/trigger on mine, although it did not report errors.

The solution was to create a separate project, using Cocoapods download the same version of Fabric, replace the run script in our project/repo (and the one referenced in the target's run script) with the downloaded version from Cocoapods. Rebuild and then the plugin would respond.

Comparing the two run script files, they are drastically different, but the run script from Cocoapods was not a flat text file and it was unreadable. So I'm not sure what was different between the scripts, but we somehow got different versions of the script while using the same version of Fabric.