XCode 14 & Firebase Crashlytics

Since I rely on Apple to sign the apps, I'm assuming that nothing local can be used.

This is only true if you use bitcode. If you don’t use bitcode then the .dSYM files that you create locally, that get embedded in your Xcode archive when you do a Product > Archive, are valid for your App Store app.

The significant change here is that Xcode 14 has effectively nixed bitcode as a concept. See the comment in the Xcode 14 Release Notes.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

This sounds like great news to me! But to be clear the I completely understand you: I should disable bitcode in my app (I’ve seen guidance on that). Then, the local dsym files can be used with Crashlytics?

I should disable bitcode in my app (I’ve seen guidance on that).

I’m not DTS expert on bitcode, nor do I work for App Review so I can’t make definitive statements on their behalf, but my take on this is that:

1. If App Review follows historical patterns, they will at some point require you to submit with the iOS 16 SDK.

2. To do that you have to use Xcode 14.

3. And, per the releases notes, that doesn’t do the bitcode thing.

Given that, you might as well get a head start on the bitcode-ectomy.

Then, the local dsym files can be used with Crashlytics?

I can’t offer any insight in to third-party crash reports — honestly, I think you should avoid them, for reasons I outline in Implementing Your Own Crash Reporter — but I will say that, if you don’t use bitcode, the .dSYM files in your Xcode archive are sufficient to symbolicate your app’s symbols in any Apple crash reports you get.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Thank you for sharing the link to your post, regarding reports in the Organiser any advices on how to see the reports of a version that was not archive on my Mac directly, on CI for example?

You’ll have to talk to your CI folks about how you can access the .dSYM files that it generated as part of its build process.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Hi eskimo, Sorry for hijacking this ticket but I have a counter question to your response.

_`Since I rely on Apple to sign the apps, I'm assuming that nothing local can be used. This is only true if you use bitcode. If you don’t use bitcode then the .dSYM files that you create locally, that get embedded in your Xcode archive when you do a Product > Archive, are valid for your App Store app.

The significant change here is that Xcode 14 has effectively nixed bitcode as a concept. See the comment in the Xcode 14 Release Notes.`_

My Question is that We have the requirement of keeping bitcode enabled until a SaaS service we are using comes up with an enhancement to Apple's change. Can you please explain why the local .dSYM won't work if bitcode is enabled? Is there anything we can do to successfully symbolicate our crash reports with Enable bitcode and Xcode 14 as we don't get the option to download them in iTunes Connect now?

Sorry for hijacking this ticket

Ha! I have the answer to that (-:

I discussed your specific issue with DTS’s tools expert and he recommended that you open a DTS tech support incident for this.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"