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.

I was experiencing an issue, so I removed the frameworks and decided to start over and try a fresh install. But the Fabric app updated to a newer version, and now when I try to reinstall Crashlytics into my app, it doesn't give me the option to reinstall the frameworks. It goes straight from clicking "install" to the "Build your project" screen, which I cannot pass.

To help configure your project, please build it now by pressing ⌘B

I press ⌘B, it builds and nothing happens. I think the issue is because I removed the Crashlytics and Fabric frameworks from my project, but I can't see a way to add them back again. The Fabric app doesn't give me that option.

Joniejonina

@MikeB: All I am seeing is "Now let's update Crashlytics", with no option to actually add a new app later. Update flow just does not work due to duplicated symbols. How do I get a correct version of Crashlytics framework which works nice with Fabric? – Fulton

@MatejBalantič odd to hear that you're seeing duplicated symbols. Try removing the current copies of the framework. Also the step I mentioned earlier would also function as a repair mode to get you back up and running. – Superb

I want to say the MAIN issue here is when you try this with a .xcworkspace. The reason being that if you open from Crashlytics it opens your .xcxcodeproj. – Caliph

Using Xcode 10.2, the answers below stop working again. Have to install Fabric using manual method. – Basilicata

@Basilicata is right. This stopped working with Xcode 10.2 w/ Cocoapods. Haven't tried installing Fabric manually (and it's not something I'm keen to do). – Incidental

@Incidental it's easy. Just drag the 2 frameworks to Xcode, add the Build Phase Script, and compile. Better than stuck waiting for Fabric's fix. – Basilicata

Answer 1

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.

Superb

I have related problem. I had project at old mac. added fabric created build with Beta and all that good stuff. as mentioned in dos. dont copy framework in project. I didnt. project run fine on old mac. but when I clone repo to another mac. I just can compile. My app shown in the list on new mac tho. its stuck on "To help configure your project, please build it now by pressing ⌘B" as I cant build because fabric.h is missing. any suggestion for me? i tried using add new app. get error screen says can add. contact support :( – Parasynapsis

Sounds like something was corrupted when getting the new files in. Using my answer above should help fix it on the new machine as well without affecting anything else. – Superb

I tried adding new app where it already showing my app in list. First thing that I never had that project in new machine. if its reading from fabric website fine. but then I get stuck on build and spinner is spinning waiting project to get compile which it wont as Fabric.h is missing. And its happening with all the projects. as soon as I clone repo somewhere else except host machine(where fabric was added to project). All are broken. – Parasynapsis

Yea, that sounds like there could be hardcoded paths breaking the path to the underlying framework or symlinks are being broken. – Superb

is there anything on Fabric website related to that? All I could find out was support email and with free account how much support I am going to get. I am not sure about that :(. Any pointer for me. which direction I should go ? – Parasynapsis

We're actively supporting Fabric Alix and all accounts are free! Drop me a note, I'm waiting for it. – Superb

I have sent msg. referring this post and chatting with you here. – Parasynapsis

@MikeB can we just create app on the web and use Cocoapods, I don't like the Fabric Mac app – Wheelbarrow

Have you guys solve this problem yet? I have the same problem, and cannot follow your steps above cause I cannot build my app due to "framework not found Fabric" error. And also definitely love to have Fabric in Cocoapods. – Sprightly

Can you drop me a note at support@ with more details on how your project is setup and what frameworks you have included? – Superb

Same kind of problem on the Android side in 12/14/2015 -- six months after being reported on iOS. #34259481 – Endosmosis

@Demigod happy to help sort out what's going on. Did you also post at TwitterCommunity? – Superb

I used Fabric in my App .. is it possible to add Fabric in my SDK that i am using for my App as well ? – Authorship

Has there been a solution found to this? I can't progress any further :( – Thorazine

@Thorazine if you're still hitting issues after trying the various solutions in the thread it's best to contact support(at)fabric(dot)io so the team can assist. – Superb

We moved onto a different solution. We just dont have the time or money to debug other peoples products. Particularly if we're supposed to trust that product to test our own products. If it can't install, its not in the running. – Thorazine

You should use whatever tool and platform best suits your needs. The circumstances that can cause this problem are not present if you use Crashlytics via Firebase which is the recommendation given Fabric's upcoming retirement in 2019. – Superb

Answer 2

Go into Build settings of the your target. Find "Debug Information Format". Set this from "DWARF" in both debug and release to "DWARF with dSYM File"

Smelser

Thank you! This is the fix for Xcode 10 and Mojave! – Vallonia

THIS IS THE ANSWER I'VE BEEN LOOKING FOR, NOTHING ELSE WORKED! – Poulenc

Yep this did it for me. This really ought go in the instructions,. – Thorazine

This should be part of the documentation. Thanks a lot. – Especially

This answer needs to be marked as correct one instead! – Kerbstone

This makes Fabric app to crash with xcode 10 and Mojave – Milkweed

This is the correct answer, really wish it was higher. Took me way too long trying the answers above. – Denn

This is a great example of how the world would grind to a halt without SO. While I love trying to figure things out for myself, I'm not sure I would EVER have landed on this solution. – Hydrostat

That's a better answer than Mike from fabric.. – Lightfoot

This is not working for me. Can anyone suggest, what else can be done here to solve this problem? Thanks – Ruvalcaba

Answer 3

If you check the resource navigator you may see the following message:

"DEBUG_INFORMATION_FORMAT should be set to dwarf-with-dsym for all configurations. This could also be a timing issue, make sure the Fabric run script build phase is the last build phase and no other scripts have moved the dSYM from the location Xcode generated it. Unable to process eCreditWebWrapper.app.dSYM at path"

Go to Build Settings and search for "Debug Information Format". Ensure "Debug" is set to "DWARF with dSYM File".

Without the dSYM file Fabric won't work.

Continuum

Answer 4

As for Xcode 10.2.1, the automated installation via Fabric Mac app won't work anymore. New apps cannot be added via the New App Step-by-step guide.

You have to follow the manual installation instructions. Download and add the 2 frameworks into your Xcode workspace, then add the Run Build Script phase (and related Fabric codes), then build the App. Last (very important), run the app in an actual device.

Once the App is successfully launched, the new App information will be available in the Fabric dashboard as well as the Fabric Mac App (needs to relaunch the App to see the new app).

---

Here are the steps:

1. Download the 2 frameworks
2. Drag to your project where your App Delegate is (make sure ticked "Copy items if needed")
3. Compile the project / workspace in Xcode
4. Add the "Run Script Phase" as instructed here; note that Xcode 10+ requires an extra configuration at Input Files
5. Add the required import and initialization codes in App Delegate
6. Add the Fabric API keys in Info.plist
7. Compile again
8. Run the App in a real device. You will see the line Crashlytics in the Xcode log. If no log appears, checks if your active scheme contains OS_ACTIVITY_MODE settings. Set it to default if the current setting is disabled.
9. If the Crashlytics line appears, that means the manual installation is working; you will see your App appearing at Fabric online dashboard.

Basilicata

I have done as the instruction. Still not working. other suggested solution are also not working. you have any idea? – Telamon

I have added the steps in my answer. hope it helps. – Basilicata

Hi @Basilicata I figured something was not working with the newest Xcode version... I followed your steps and I see in the logs stuff like: [Crashlytics] Version 3.13.4 (143) [Crashlytics] Running on iPhone10,6, 12.2.0 (16E227) [Fabric] Initialized with kit versions: { "com.twitter.answers.ios" = "1.4.1"; "com.twitter.crashlytics.ios" = "3.13.4"; "io.fabric.sdk.ios" = "1.10.2"; } ` [Fabric] settings downloaded successfully` .... But still doesn't show on my dashboard – Ruggiero

It should show in Fabric dashboard. Make sure you choose the right app in the dashboard. – Basilicata

Running the app on the device is critical. To also get my first crash report, it was necessary to implement the code that force crashes and then redeploy to the device (as opposed to reopening the app on the device itself), as relaunching the app via XCode is what sends the crash report. – Frazzled

Answer 5

I have solved this issue by the following way. Following the advise from above, I began adding a new app to crashlytics. When I reached to adding new "Run script" build phase, I just copied that text and pasted it over the previous one(created with Crashlytics). I have also unchecked "Run script only when installing".

After this, I canceleed adding a new app and procedeed back to the UPGRADE. At this moment, building the app, can pass you to the next step and you don't get stuck on that screen anymore.

Indifferent

Doesn't help as well. – Demigod

Answer 6

I was stucked on Build phases too.

I have also unchecked "Run script only when installing" and press again command+B and then I passed to the next step.

Robbins

This was all I needed to do! Much simpler than recreating a new app and reinstalling everything... – Nydia

Answer 7

If the script is not running, you may have checked the "run script only when installing" in the run script section. I hope it helps

Privilege

In Xcode 12 it's called "Based on dependency analysis". It started working for me when I have UNCHECKED it. – Spock

Answer 8

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.

Gainey

Answer 9

I had the same issue today. The problem was that i didn't have the run-script :

./Fabric.framework/run <api key>

in my project. Once i put this back in then it all worked perfectly. I also cleaned my project and deleted derived data just to be sure.

Morelos

And it has to be at line #1 – Nebuchadnezzar

Answer 10

you must check that your deployment target version because of "Fabric's minimum iOS version is 6.0"

Ailis

Answer 11

I was only able to get the Fabric app to continue the installation process after setting my build target to 'Generic iOS Device' and creating an archive from the Product > Archive menu.

Simply building the app or running it on an emulator doesn't seem to trigger the Fabric App to proceed.

Facility

setting the build target to "Generic iOS Device" and probably setting the Debug Information Format to "DWARF with dSYM File" actually solved the problem for me – Rhubarb

Answer 12

If you use Xcode 10.

Project Navigator -> your project -> Targets -> Build Phases -> your Run Script for Fabric -> Input Files -> "+" (add input file) -> clear field and past this line:

$(BUILT_PRODUCTS_DIR)/$(INFOPLIST_PATH)

Be sure to remove this: $(SRCROOT)/

Zondra

Answer 13

In the Run Script build phase there is a call:

./Crashlytics.framework/run <your_api_key_here>

Maybe you added some conditions to trigger it only on certain builds like:

releaseConfig="Release"

if [ "$releaseConfig" = "${CONFIGURATION}" ]; then  
    echo "Running Crashlytics"
    ./Crashlytics.framework/run <your_api_key_here>
fi

so that it will not just trigger on ⌘B

See https://dev.twitter.com/crashlytics/ios/advanced-setup

Pavior

Answer 14

In my situation I was following all the steps correctly but got stuck on 'add build phase' step. Then I just restarted fabric and all works just fine

Also there are some other possible actions:

1) Just restart Fabric, Xcode and your Mac. 2) Also if you use Cocoapods change build phase line from

./Crashlytics.framework/run [yourAPIKey] 

to

"${PODS_ROOT}/Fabric/run" [yourAPIKey]

3) After building project if Fabric will stop responding just wait a while. It took about minute on my Mac.

Harelip

Wow. I just spent an hour trying to debug this, and this was the reason why. – Brazzaville

The bit about the Fabric app not responding, thought it had crashed but I just wasn't patient enough. – Haze

Answer 15

Thanks, I solved the problem by removing folders:

~ / Library / Caches / com.crashlytics.data
~ / Library / Caches / com.crashlytics.mac

Portcullis

Not to forget this ~/Library/Caches/io.fabric.sdk.mac.data as well – Basilicata

Answer 16

Kindly cross verify that run script you adding is to your actual target if u will add to tests target it will not proceed until you add it to actual target

Yellowthroat

Answer 17

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.

Cruz

Answer 18

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.

Xenomorphic

Answer 19

If you are duplicating the target, remove the run script from build phase and add it again to solve the issue.

Cartage

Answer 20

If you have multiple TARGETS,

check your Schema selection is correct before you build project.

Biometry

Answer 21

For Xcode 10. Add your app's built Info.plist location to the Build Phase's Input Files field:

$(BUILT_PRODUCTS_DIR)/$(INFOPLIST_PATH)

This solved my issue i hope this can solve others issue.

Grieco

Answer 22

It turned out I had not enough permissions to create new project in Fabric. Upgrading from Member to Admin resolved the issue.

Colossae

Answer 23

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.

Sulamith

Answer 24

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

Peres

Answer 25

Open Project in higher version of Xcode. This resolved my issue after waste many hours.

My Project build on Xcode 10.2 and I was running on Xcode 10.1 but when I run the same project on Xocode 11. The build was succeeded.

Strophanthus

Answer 26

Try to wrap your run script variable with double quotes ""

"${PODS_ROOT}/Fabric/run"

Loaning

Answer 27

Go to folder /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/<CURRENT_IOS_SDK>/usr/lib/ and delete all .dylib files.

It worked for me.

Personification