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

Post not yet marked as solved Up vote post of Purcy Down vote post of Purcy
15k views
Posted by
Purcy
Reply

  • 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.

    —
    bkirby_abra

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

    —
    Hue Essentials

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

    —
    scott222

Apple 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.

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"

Posted by
eskimo
Post not yet marked as solved Up vote reply of eskimo Down vote reply of eskimo
Post marked as Apple Recommended
Add a Comment

Replies

Like some others here my DSYM download link has now shown up as well. It took roughly 5-6 days to show up. I didn't upload a new build or change any configuration. The only thing I did was raise a support request a couple days ago. There is no activity on the request, so I can't confirm whether that is responsible for the link showing up, of if it was just a coincidence. So not really a proper solution or satisfying outcome as the cause and fix are still unknown. Would still like to see if anyone from Apple can chime in here and hopefully explain the issue in more detail and potential mitigations that can be taken.

Posted by
Purcy
Up vote reply of Purcy Down vote reply of Purcy
Add a Comment

I submitted a ticket to Feedback assistant, and someone replied yesterday that the issue had been resolved. I guess we'll find out on the next submission.

Posted by
scott222
Up vote reply of scott222 Down vote reply of scott222
Add a Comment

We are experiencing this issue in August, was this resolved?

Posted by
Mo7102
Post not yet marked as solved Up vote reply of Mo7102 Down vote reply of Mo7102

  • Same for us! Latest build isn't showing option to download symbols. Builds from a few days were working fine.

    —
    pyraego

  • Same here! Latest build is not showing option to download symbols.

    —
    mikemike396

  • same here! I can't find download link :(

    —
    lucyjeong
Add a Comment

Same here! No download button visible. The flag "Include symbols" says "YES". Even trying with App Store Connect API we weren't able to donwload anything as the dsymUrl returned is "None".

Can someone provide support to this? We really need that file to upload it on Firebase/Crashlytics.

Posted by
arossini
Post not yet marked as solved Up vote reply of arossini Down vote reply of arossini
Add a Comment

It seems this issue consistently occurs if building with Xcode 14...

Posted by
zendaya
Post not yet marked as solved Up vote reply of zendaya Down vote reply of zendaya
Add a Comment

According to release notes of Xcode 14 "Bitcode is Deprecated."

https://developer.apple.com/documentation/xcode-release-notes/xcode-14-release-notes

Since Bitcode is not enabled anymore, I think Apple is stopped producing DSYM files for builds produced by Xcode 14.

Posted by
mindsoftdev
Post not yet marked as solved Up vote reply of mindsoftdev Down vote reply of mindsoftdev

  • So what am I supposed to do now? where can I get the DSYM ?

    —
    EliLeshem

  • Since Apple does not processing our builds for bitcode setting, we don't need to get any DSYM file from Apple anymore. You can use DSYM files produced in your local machine in order to symbolicate any crash.

    —
    mindsoftdev
Add a Comment

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

Posted by
Gong
Up vote reply of Gong Down vote reply of Gong
Add a Comment

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?

Posted by
appletester123123
Up vote reply of appletester123123 Down vote reply of appletester123123
Add a Comment

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

Posted by
panchapakesan
Up vote reply of panchapakesan Down vote reply of panchapakesan
Add a Comment

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

Posted by
Shyamgosavi
Up vote reply of Shyamgosavi Down vote reply of Shyamgosavi
Add a Comment

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

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

Enjoy ;)

Posted by
AntoninMarek
Post not yet marked as solved Up vote reply of AntoninMarek Down vote reply of AntoninMarek

  • That pulls prod crashes?

    —
    myakavenka

  • heyy, thank you for the information 🙋🏻‍♂️, eventually find.

    —
    matalay
Add a Comment

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

Posted by
JerryBocc
Up vote reply of JerryBocc Down vote reply of JerryBocc
Add a Comment

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"

Posted by
eskimo
Post not yet marked as solved Up vote reply of eskimo Down vote reply of eskimo
Post marked as Apple Recommended
Add a Comment