ASC Doesn't generate DSYM file

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"

I'm seeing the same thing. I wonder if it's related to the new submission system. It changed recently to allow multiple submissions at the same time. This was the first build using this new system that is missing dsyms.

Same issue here. Already submitted multiple builds but still no debug symbols available for download.

We've also submitted two different apps on Friday and neither of them have dSYMs as of today (monday)

+1

+1 I saw the generated DSYM showing up after, maybe, 10, 12 hours. Hope it will get fixed soon

Same here, last build that worked was uploaded on February 5th

I submitted a bug report, FB9889200. Would be great if everyone can do so, so that Apple reacts more quickly.

+1

Thanks for letting us know! Our teams are looking into this. To stay updated on the progress and help with the investigation, please be sure to file a feedback report or contact support directly.

We are experiencing the same problem. We have submitted our build about 24 hours ago. We still do not have any available DSYM files for download.

Same here, tried several times(builds) but dSym link is not showing up!

+1. It started happening randomly around February 3 (JST), and since February 8 (JST), none of the builds have generated dSYM!I had to increment a lot of build versions to try this out... I had to reorganize my version control... (I had to patch the marketing version or something, even though it wasn't a patch for the app)

We are experiencing the same problem, tried several times(builds) but dSym link is not showing up!

Experiencing the same issue across several apps and builds.

We had the same problem, we couldn't download DSYM files in the background of App Store Connect.

ASC Doesn't generate DSYM file
 
 
Q