Crashlytics on iOS won't pass Build Your Project in Fabric app

Question

I install Crashlytics for my iOS application. I downloaded it via the link to my website and went through all the steps to integrate the frameworks, adding a script run, etc.

I had a problem, so I removed the frameworks and decided to start all over and try a new installation. But the Fabric application has been updated to a newer version, and now when I try to reinstall Crashlytics in my application, this does not allow me to reinstall the frameworks. This happens immediately after clicking the "install" button on the "Create your project" screen, which I cannot transfer.

To set up a project, please create one by pressing ⌘B

I press ⌘B , he builds and nothing happens. I think the problem is that I removed the Crashlytics and Fabric framework from my project, but I see no way to add them back. The Fabric app does not give me this opportunity.

Answer 1

Transition from comment to response.

Mike from Cloth. If you back up using the Mac app, click on the arrow in the upper left corner, click on “+ New app” and you will re-add everything.

Answer 2

Go to the build settings of your goal. Find "Debugging Information Format". Set this value from "DWARF" in both cases of debugging and release to "DWARF with dSYM file"

Answer 3

If you check the resource navigator, you can see the following message:

"For all DEBUG_INFORMATION_FORMAT configurations, dwarf-with-dsym should be set. This can also be a synchronization problem, make sure that the build phase of the Fabric startup script is the last build phase, and no other scripts have moved dSYM from the location created by Xcode .. Not managed to process eCreditWebWrapper.app.dSYM along the path "

Go to "Build Settings" and find "Debugging Information Format". Verify that Debugging is set to DWARF with dSYM file.

Without a file, dSYM Fabric will not work.

Answer 4

I solved this problem as follows. Following the recommendations from above, I began to add a new application for starters. When I got to adding the new Run script run phase, I just copied this text and pasted it on top of the previous one (created using Crashlytics). I also unchecked "Run script only on installation".

After that, I can add a new application and return to UPGRADE. At the moment, when creating the application, you can go to the next step, and you will no longer be obsessed with this screen.

Answer 5

I, too, got stuck at the assembly stages.

I also unchecked the "Run script only when installing" checkbox and clicked the + B command again, and then moved on to the next step.

Answer 6

If the script is not running, you can check the "run the script only during installation" section of the script. I hope this helps

Answer 7

For Xcode 10.2.1, unattended installation through the Fabric Mac application will no longer work. New applications cannot be added using the New Application walkthrough.

You must follow the manual installation instructions . Download and add 2 frameworks to your Xcode workspace, then add the Run Build Script phase (and the corresponding Fabric codes), then create the application. Last (very important), run the application on a real device.

After the application launches successfully, information about the new application will be available on the Fabric toolbar, as well as in the Fabric Mac application (you must restart the application to see the new application).

---

Here are the steps:

1. Download 2 frameworks
2. Drag and drop in your project where your application delegate is located (check the box "Copy items if necessary")
3. Compile project / workspace in Xcode
4. Add "Run Script Phase" as indicated here ; note that Xcode 10+ requires additional configuration in Input Files
5. Add the necessary import and initialization codes to the App Delegate
6. Add Fabric API Keys to Info.plist
7. Compile again
8. Run the application on a real device. You will see the Crashlytics line in the Xcode log. If the log is not displayed, checks if your active configuration scheme OS_ACTIVITY_MODE . Set default to default if the current setting is disabled .
9. If the Crashlytics line appears, it means that manual installation works; your application will appear in the Fabric online control panel.

Answer 8

TL; DR

Click on your schema → change schema → set build configuration to “Release”

Explanation:

The answer with the most votes sounds plausible, but there are situations when you just don't need crashes in debug builds (who wants crashes to go when you're just developing and experimenting with your code?). In this case, you should disable the crash by checking the debug compilation flags (beyond the scope of this answer) and for the first time during installation, build the release application so that the crash knows that you created the application.

Answer 9

I had the same problem today. The problem was that I did not have a run-script:

 ./Fabric.framework/run <api key> 

in my project. As soon as I put it back, then everything worked perfectly. I also carefully cleaned my project and deleted the data.

Answer 10

you must verify that your target deployment version is because "Minimum iOS Version for iOS Version 6.0"

Answer 11

I was able to get the Fabric application to continue the installation process only after I selected “Generic iOS device” for my build purpose and created an archive from the Product> Archive menu.

Just creating an application or running it on an emulator does not launch a Fabric application.

Answer 12

At the script build stage, a call is made:

 ./Crashlytics.framework/run <your_api_key_here> 

You may have added some conditions to cause it only on some assemblies, for example:

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

so that it does not start only on ⌘B

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

Answer 13

In my situation, I followed all the steps correctly, but got stuck in the "add build phase" phase. Then I just restarted the fabric and everything works just fine

Other possible actions are also possible:

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

 ./Crashlytics.framework/run [yourAPIKey] 

to

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

3) After creating the project, if Fabric stops responding, wait a while. It took about a minute on my Mac.

Answer 14

If you are using Xcode 10 .

Project Navigator → your project → goals → build steps → your startup script for Fabric → input files → “+” (add input file) → clear the field and skip this line:

 $(BUILT_PRODUCTS_DIR)/$(INFOPLIST_PATH) 

Be sure to remove this: $(SRCROOT)/

Answer 15

Tell me, please, run the script, adding to your actual target, if u adds testing to the target, it will not work until you add it to the real target.

Answer 16

None of the solutions worked here. The script for me was someone else, adding the Fabric framework to our project and passing it a repo. Running the script on their computer started / started the Fabric plugin, but did not start / started on mine, although it did not report errors.

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

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

Answer 17

I was mistaken when adding a script to the build phase of the pods project instead of the build phase of the main project , adding it to the main build phase of the project is a problem.

Answer 18

Thanks, I solved the problem by deleting the folders:

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

Answer 19

If you duplicate the target, remove the startup script from the build phase and add it again to solve the problem.

Answer 20

If you have several goals,

Verify the correct schema selection before creating a project.

Answer 21

For Xcode 10. Add the Info.plist location created by the application to the Build Phase Input Files field:

$ (BUILT_PRODUCTS_DIR) / $ (INFOPLIST_PATH)

This solved my problem, I hope this can solve other problems.

Answer 22

It turned out that I did not have enough rights to create a new project in Fabric. Upgrading from Member to Admin resolved the issue.

Answer 23

In my case, uninstalling the application from helped. 1) Remove the application from the fabric. 2) Again, follow all the steps to add the application and install Crashlytics.

Answer 24

Nothing helped me. Fabric now catches my archive creation. But I create archives through fastlane build_app .

Answer 25

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

It worked for me.