Crashlytics does not report a failure in Release mode

Question

Crashlytics was installed in this application for several releases. It works great.

But when we prepare the next version, Crashlytics stopped reporting failures in Release mode. Here is what I can think of that has changed since our last release.

• Xcode 7.1. The latest version was prepared using Xcode 6.
• We upgraded to Fabric.
• We are testing the application on iOS 9.1.

In any case, with all these changes, debugs still report fines. Just not in release (installation from TestFlight after archiving and downloading to iTunes Connect).

Here is what I checked:

• There is an application on the Fabric website, there is a version and an assembly. When I click Missing DSYM, he tells me that they are not there.

• startWithAPIKey is called in didFinishLaunchingWithOptions (added after the trojanfoe question).

• The api key is correct. Checked and double checked.

• There is no (and never was) difference in the build of the script between Debug and Release. It looks like this:

• The DEBUG_INFORMATION_FORMAT assembly DEBUG_INFORMATION_FORMAT have already been set to DWARF with dSYM File (added after the StormXX question):

What am I missing?

Answer 1

Mike from Crashlytics and Fabric is here.

With Fabric, Crashlytics initialization has changed a bit. Using the following code should work (Obj-C):

 #import "AppDelegate.h" #import <Fabric/Fabric.h> #import <Crashlytics/Crashlytics.h> @interface AppDelegate () @end @implementation AppDelegate - (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions { // Override point for customization after application launch. [Crashlytics startWithAPIKey:@"YourAPIKey"]; // You can comment out the above line if you have your Twitter Fabric API key in your info.plist. [Fabric with:@[[Crashlytics class]]]; return YES; } 

It is also recommended that you update the build phase of the script as follows:

 ./Fabric.framework/run <YourAPIKey> <YourBuildSecret> 

Answer 2

I also ran into this problem. My DSYM application files were not automatically uploaded to Fabric, as they were before. It was discovered that the main reason was that xcode 7.1 defaulted the project for bit code enabled = YES

Bitcode setting enabled = NO in my build settings fixed the problem of automatic loading.

From the advanced Fabrics setup document :

Bit-code-enabled applications are needed to download their dSYM from Xcode, and then load it into Crashlytics so that we can symbolize crashes.

Answer 3

I encountered the same problem, and I am parsing it ... Check your project "Build setup", find the Debug information format . change it to DWARF with dSYM file

Picture

Answer 4

I was unable to load dsym files from .xcarchive. Only when I downloaded the zip dSYM archive from iTunesConnect and loaded it into fabric does it make sense.