Crashlytics has been installed in the app in question for a couple of releases now. It's been working great.
But as we prepare the next release Crashlytics has stopped reporting crashes in Release mode. Here are the things I can think of that have changed since our last release.
Anyway, with all those changes crashes are still being reported just fine in Debug. Just not in Release (installing from TestFlight after archiving and uploading to iTunes Connect).
Here are the things I've 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
(added after trojanfoe's question).
The api key is correct. Checked and double-checked.
In the build script there isn't (and never was) a distinction between Debug and Release. It looks like this:
DEBUG_INFORMATION_FORMAT
is already set to DWARF with dSYM File
(added after StormXX's question):What am I missing?
I was also facing this issue. My apps DSYMs files were not being automatically uploaded to Fabric as had previously been the case. The root cause was found to be that xcode 7.1 had defaulted the project to bitcode enabled = YES
Setting Bitcode enabled = NO in my Build Settings fixed the auto upload issue.
From Fabrics advanced set up document:
Bitcode enabled applications are required to download their dSYM from Xcode and then upload it to Crashlytics so that we can symbolicate the crashes.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With