Build Servers

We support Jenkins and XCode Bots right out of the box. Onboard your app using Fabric, push to your server and we’ll receive your dSYMs automatically.

Pro tip: Make sure that Xcode.app is closed and Crashlytics.app isn’t installed on the server.

Moving the iOS Framework

If you want to move Crashlytics.Framework to another directory, you can; just be sure to update the `Run Script Build Phase` to point to the new directory.

Example: The default Crashlytics run script build phase is:

	./Crashlytics.framework/run <your_api_key_here>

If you move the Crashlytics framework one level down, to a directory called “Vendor”, you’ll need to modify the run script build phase to be:

	./Vendor/Crashlytics.framework/run <your_api_key_here>

You can use our XCode Build Phase Cheat Sheet to help.

Conditional dSYM Upload

The default set up process ensures that we get your app’s dSYMs on every build (assuming a code change). This is the preferred configuration, so that if a crash comes while you develop and do internal testing, we can show you the exact line of code that caused the crash.

However, if you would like to run Crashlytics only on certain builds, you can add logic to the run script build phase to only run when desired. Try something similar to:

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

Uploading dSYMs Manually

If you find that dSYMs aren’t being picked up, you can add them manually by going to your app settings page](https://fabric.io/settings/apps), selecting an app, and appending “mappings” to the end of the URL, e.g.:

https://fabric.io/settings/apps/<my_app_id>/mappings

This will take you to a page where you can manually upload your dSYMs.

Multiple Targets

To run Crashlytics with multiple targets, add a Crashlytics Run Script to each target’s Build Phase. The default Crashlytics run script build phase is:

	./Crashlytics.framework/run <your_api_key_here>

Apps with Multiple Environments

Let’s say you have an app called MyAwesomeApp and you want to keep the bundle id the same, even though you have a staging, dev and prod version of your app.

The easiest thing to do is create a separate organization for each version, onboard each version of MyAwesomeApp to the corresponding org (just make sure you grab the new API key for each org) and you’re all set.

Why do it this way?

• Keeps your crashes separated by org
• Add different team members to each org to control who has access to prod vs staging, etc.

Privacy Dialog

By default, this feature is disabled. When a crash occurs in any version of your app, this will ask your users if that crash should be reported. Our analytics data shows that most users will decline to report crashes, so we recommend leaving this disabled. If you’d like to enable it, you can do it in your app settings page.

Advanced

If you want to localize the “Send Crash Report” dialog within Crashlytics, then your app must include a standard strings file called “Crashlytics.strings” in your project’s localizable resources.

We use the following keys:

• “CrashlyticsCrashSubmissionPromptTitle”
• “CrashlyticsCrashSubmissionPromptMessage”
• “CrashlyticsCrashSubmissionSendTitle”
• “CrashlyticsCrashSubmissionAlwaysSendTitle”
• “CrashlyticsCrashSubmissionCancelTitle”

The presence of any one of these keys for any language will override any settings in our web UI. However, you still must use the web UI to control the presence of the “always send” button and the prompt dialog itself.

Sample Crashlytics.strings file:

/* 
Crashlytics.strings
*/

"CrashlyticsCrashSubmissionPromptTitle"     = "Send Crash Report?";
"CrashlyticsCrashSubmissionPromptMessage"   = "Looks like we 
					crashed! Please help us fix the problem 
					by sending a crash report.";
"CrashlyticsCrashSubmissionSendTitle"       = "Send";
"CrashlyticsCrashSubmissionAlwaysSendTitle" = "Always Send";
"CrashlyticsCrashSubmissionCancelTitle"     = "Don't Send";