Crashlytics not reporting crash in Ad-Hoc/Release mode

[Swapnil Jagtap]

Hello,

We have setup the Fabric to get crash reports using Crashlytics in our iOS application, We successfully integrate and configure in app with xcode and OS version listed bellow:

• Xcode 8.3.2 
• We upgraded to Fabric.
• We're testing the app on iOS 9.0 and above

With all those changes crashes are still being reported just fine in Debug build. Just not in Release installed from iTune store and archive with Ad-Hoc build and test. For store release build on dashboard -> Latest release -> under Stability I can see the crash count but when I open in dashboard not seen any crash.

Here are the things We have checked:

• On the Fabric site the app is there, the version and build are there. When I click on Missing DSYMs it tells me there are none missing.
  
• startWithAPIKey is being called in didFinishLaunchingWithOptions
  
• The api key is correct. Checked and double-checked.
• Setting Bitcode enabled = NO in my Build Settings.
• In Build Settings DEBUG_INFORMATION_FORMAT is already set to DWARF with dSYM File(added after StormXX's question):

• Initialization of Crashlytics in app delegate
• [Crashlytics startWithAPIKey:@"YourAPIKey"];   
•   [Fabric with:@[[Crashlytics class]]];

• In the build script there isn't (and never was) a distinction between Debug and Release. It looks like this:

What we missing and what was the root cause?

[Arkadiy]

I've run into the same issue, and apparently this is the only place where it has been reported. Have you found any solution to this problem?

[Todd Burner]

Hi, 

Todd from Fabric here. Can you try removing your [Crashlytics startWithAPIKey:@"YourAPIKey"];  line and trying again? With Fabric that line is no longer necessary. If that doesn't work, check out the output of debug mode after you relaunch the app after a crash. https://docs.fabric.io/apple/fabric/advanced-settings/debugging.html Make sure to press stop in the Xcode and relaunch the app before causing the crash.

I suspect there is a configuration issue and you should see an error in the output of debug mode.

Thanks!