DSYMs No Longer Offered for Download?

Hi,


In February I was able to upload bitcode IPA files via application loader. Once uploaded, a short time afterwards, on ItunesConnect - if I went to Activity > App Build > Under General Information, Includes Symbols - there would be a link called 'Download dSYMs' to download my DSYMs.


Now in March - any new bitcode IPAs I upload, no longer have the download DSYMs link offered.


I've even tried reuploading an old project from Feb that generated DSYMs on ItunesConnect previously (but reuploaded it with a new build number) - but even that still fails to give a Download DSYM link.


Has this functionallity been removed from iTunesConnect?

This is happening with me as well. Any updates from @apple team?
Just to bring this up to date as of Xcode 12.2, Apple is allowing Xcode to download the symbols.

1) Go to the Organizer and find the app you uploaded to the store.
2) Click the Download Debug Symbols button beneath Details.
3) Right-click the app and Show In Finder.
4) Right-click the xcarchive and Show Package Contents
5) Your dSYMs are in the folder...
https://appstoreconnect.apple.com > APP > TestFlight > Select Version > Select Build > Build version metadata > download dSYM
Still not working for me. Can't download debug symbols in xcode, nor on ASC, nor do they exist under my .xcarchive's package contents. Any resolution here?

Still no "Download DSYM" button for me in https://appstoreconnect.apple.com > APP > TestFlight > Select Version > Select Build > Build metadata > download dSYM.

What is strange - I have two different apps on two different accounts. One account contains "Download DSYM" button for all builds, another doesn't have this button at all. DWARF with DSYM is set for both apps

Any update on this? I don't see the DSYM download link under metadata.

I found that even Debug Information set to "DWARF with dSYM" but bitcode disabled (Not included) when upload to AppStore button "download dSYM" will missing.

My problem when using Xcode 13 after Product > Archive and upload to AppStore, checkmark "Include bitcode for iOS content" is greyed out. If I clicked button next in review dialog show Bitcode: Not included -> No download button.

But if I switch back archive using Xcode 12, "Include bitcode for iOS content" isn't greyed out. Then I clicked button next show Bitcode is Included -> so button download dSYM not missing.

Hope this help.

Guys same for me apparently for some builds downloading of dSYMs isn't available anymore, any hint what could lead to this? Bug on Apple's side?

Same here, since the new “Ready for Submit” status release, some of our builds randomly didn’t get the Download dSYM link, even with including symbols…

I see the same in AppStoreConnect: "Includes Symbols Yes", but no link. I have Fastlane configured to upload symbols, but not upload nor compile Bitcode. I need the symbols to debug PROD crashes, come on ASC Team!

It appears that when using Bitcode, dSYMs are downloadable from AppStoreConnect. When not using Bitcode, the developer is responsible to keep archived apps (.xcarchive bundles) on the computer, so that dSYMs can be searched by Xcode. If you're using fastlane to archive an app, it's a good idea to call backup_xcarchive so that you have access to dSYMs in the future. For my case, i will turn on Bitcode compilation & upload, which should allow downloading from ASC later.

If you distribute your app through the App Store with bitcode enabled, your Mac won’t contain the dSYM files that match the final build, because the final compilation of your app from bitcode occurs in the App Store. This final App Store created build has a different build UUID and different dSYM files than the build in the orginial Xcode archive. Use the Xcode Organizer to download the dSYM files for the build created by the App Store.

https://developer.apple.com/documentation/xcode/adding-identifiable-symbol-names-to-a-crash-report

This happens randomly. Your best bet is to contact apple support and ask them repair it. According to their techs, it happens sometimes if their is a failure in one of their CI pipelines, so they just need to find the failed job and hit retry. This is why sometimes it will work and sometimes not, it's random based on server failure.

DSYMs No Longer Offered for Download?
 
 
Q