dsym file

It seems to work after adding dSYM File.

dSYM files are produced by the compilation of your app in Xcode. In the era of bitcode uploads to the App Store, there was a final compilation step performed by the App Store, which meant that the App Store produced the dSYM file and made it available for download. Now that bitcode is not part of the app distribution story any longer, that means the final dSYM files are the ones produced by Xcode on your Mac when you compile your app — there is nothing to download any more. To see the dSYM files produced before you upload your app to the App Store, you can look inside the .xcarchive by right-clicking on the archive in the Xcode Organizer, and selecting Show in Finder. And then in Finder, right-clicking on the archive bundle and selecting Show Package Contents. —Ed Ford,  DTS Engineer

Then I used Xcode 15.4 to built and generated .ipa again. There are .symbols files inside Symbols folder in ipa(.zip) as before, but MyApp.xcarchive/dSYMs is also empty. I'm surprised by this. Can you check the value of the DEBUG_INFORMATION_FORMAT build setting, and see if it's set to DWARF with dSYM File for your Release build. That's the standard set up for Release builds, while Debug builds default to DWARF, so there is no dSYM file. One other thing to look at is if your Archive action in Xcode is set to use your Release configuration, or if it's set to a Debug configuration. That configuration detail is found in your scheme configuration, under Archive. Additionally, could you also please kindly tell me why are there two kinds of files for generating crash reports? (.symbols files and dSYM file), do they have different aims? The dSYM file contains extremely detailed information in DWARF that enables debugging your app in minute detai

same here, no where to download the dSYM file

Did you get the problem with Xcode16.1ß1 or 16.0ß5 ? Just an idea, from this very old thread: https://stackoverflow.com/questions/29209582/make-sure-your-project-build-settings-are-generating-a-dsym-file-debug-informat Check that you create a DSYM file (go to the build settings -> Build options) Hope that helps.

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 subm

I have discovered a work-around.According to the following technical note, for debug builds, dSYM information is embeded in the application. Release builds do produce dsyms inside the .xcarchive file. https://developer.apple.com/library/content/technotes/tn2151/_index.htmlTo get dSYMs for my enterprise debug and release builds, I modified the Debug Information Format build setting to DWARF with dSYM file for debug builds.Now, when I archive a debug build (internal QA testing builds), I can right click on the archive in the organizer and select Show in Finder then Show package contents on the .xcarchive and find the dSYM file in the dSYMs folder.

Build with dsym file works for me, but this makes build time really long

i do not have dSYM files, let me collect it and check out the link

dSYM files finally popped up in ASC after five(!) days of waiting.

We need those dSYM files back as well... Please make them available again.

I get this:mdls -name com_apple_xcode_dsym_uuids Dodgers.app.dSYMcom_apple_xcode_dsym_uuids = (null)A malformed dSYM file you think?

I see dSYM files for some frameworks the app uses, as well as some of its extensions (intents, widgets) but there isn't a dSYM for the app itself. This is the issue. Verify the DEBUG_INFORMATION_FORMAT build setting (including any overrides by .xcconfig files) to make sure a dSYM is being generated.

If you’re not using App Store Connect then the whole download .dSYM files process is irrelevant to you. Your app is built locally and the .dSYM files created by that build process are all you need to symbolicate. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Steps to Resolve the Issue Here are some steps you can take to ensure that your dSYM files are included in your archive: 1. Check Build Settings: • Go to your project settings in Xcode. • Select the target for your app. • Navigate to the Build Settings tab. • Search for Debug Information Format and ensure it is set to DWARF with dSYM File for both Debug and Release configurations. 2. Clean the Build Folder: