ASC Doesn't generate DSYM file

App Store Distribution & Marketing App Store Connect App Store Connect Organizer Window

Created Feb ’22

Replies 39

Boosts 8

Views 18k

Participants 40

The latest build of my iOS app in TestFlight does not show a "Download DSYM" link in the build metadata tab. When I uploaded the build to App Store Connect I had "enable bitcode" turned on, and I can see "Include Symbols" is set to yes in the build metadata. But no link is next to it like my other recent builds.

The last few builds I've submitted in the same manner have all generated the DSYM download links no problem. For some reason this particular build has not.

Has anyone else experienced this same issue? Any tips of how to fix this? I'd like to avoid submitting a new build if possible

Cheers

Answered by DTS Engineer in 767515022

is there a fix available?

There’s nothing really to fix here. Lemme explain…

In general:

You are responsible for building the binary that you submit to the store.
That build process creates a .dSYM file that matches that binary.

If you’re using Xcode, both the binary and its .dSYM file end up within your Xcode archive.

Historically, Apple allowed, and in some cases required, apps to submit as bitcode. Apple then recompiled the app from that bitcode, and distributed that binary to end users.

That caused problems for symbolication because the binary being run by end users didn’t match the .dSYM file in your Xcode archive. To solve this, Apple created a mechanism for you to download a .dSYM file for the binary that Apple generated.

With Xcode 14, so about a year ago, Apple stopped doing the bitcode thing. To quote the Xcode 14 Release Notes.

Starting with Xcode 14, bitcode is no longer required for watchOS and tvOS applications, and the App Store no longer accepts bitcode submissions from Xcode 14.

So, the whole reason for downloading .dSYM files is now gone, and folks can go back to what they used to do before bitcode was a thing: Build the binary and it’s .dSYM locally and use that for symbolication.

If you have a process that relies on getting a .dSYM file from Apple, please update that process to work with your locally built file.

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

Boost

Gong OP

Sep ’22

This issue has been bothering me for weeks. Finally I found dSYM in the Artfact of Xcode Cloud workflow...

appletester123123 OP

Oct ’22

I'm experiencing this currently. I released an app version on Friday 21st Oct, and it is Monday 24th and nothing is showing on TestFlight or via the XCode Organiser. Is there an update on this?

panchapakesan OP

Nov ’22

I am also facing the same issue on appstore connect not able to see the "download dSYM" button. Is that not resolved yet?

Shyamgosavi OP

Nov ’22

Anyone got any solution for this problem, I am not able to see download dSYM option in TestFlight, also I tried from organiser -> selected build -> Download dSYM but I am getting message "Their is not dSYM found."

Can anyone help me on this.

@Apple support please provide any solution on this problem

AntoninMarek OP

Jan ’23

For everybody who need quick fix... I fix this problem with this solution:

Open "Organizer" in XCode menu - menu>window>organizer
Select your IPA build and with right mouse click select "show in finder"
On generated file with right mouse click select "show package content"
Comprim DSYM directory to .zip file and move him outside the package for use tham, where you need it.

Enjoy ;)

Joohae Kim OP

Mar ’23

I'm not sure the issue has been fixed but I have the issue on my TVOS app

JerryBocc OP

Oct ’23

I still can repro this issue - is there a fix available ? thanks so much -

DTS Engineer OP

Apple

Oct ’23

Recommended

is there a fix available?

There’s nothing really to fix here. Lemme explain…

In general:

You are responsible for building the binary that you submit to the store.
That build process creates a .dSYM file that matches that binary.

If you’re using Xcode, both the binary and its .dSYM file end up within your Xcode archive.

Historically, Apple allowed, and in some cases required, apps to submit as bitcode. Apple then recompiled the app from that bitcode, and distributed that binary to end users.

With Xcode 14, so about a year ago, Apple stopped doing the bitcode thing. To quote the Xcode 14 Release Notes.

Starting with Xcode 14, bitcode is no longer required for watchOS and tvOS applications, and the App Store no longer accepts bitcode submissions from Xcode 14.

If you have a process that relies on getting a .dSYM file from Apple, please update that process to work with your locally built file.

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

azaazazaz OP

Sep ’24