dsym file

I have also faced same issue while downloading the dSYM. I have found my dSYM under TestFlight build section. Check my post here - https://stackoverflow.com/questions/65210768/from-where-i-need-to-download-the-dsym-from-app-store-connect

It seems that if I download the zip file with a MAC I get both the .json and the .crash ! Doing exactly the same on Windows gives me only the .json. Is it the same for you ? It is really annoying as the crash file can be used out of xcode context (for example it can be uploaded to AppCenter along with the dsym ...)

This could be the sign of a mismatched dSYM with your binary. You're not expecting a binary inside the framework because you say it was linked statically...but is there a binary in the framework in a way you don't expect, sending you down this path? To rule that out, I'd dig around inside the framework contents inside of your Xcode archive to see if there's a binary still in there. If there is, check the binary UUIDs match, as that's the identifier that ties everything together for symbolication. You can use the dwarfdump --uuid command to get it from your framework binary, and then again to the DWARF file nested inside the dSYM package. I would dig around inside the the build Xcode archive from the Organizer to locate those files for this test, rather than relying on any files in your source code base, since the Xcode Archive's contents is what the App Store sees. If that leads to a dead end, then I suggest you study your build log to see if you can find any trace

Facing the same issue.Error Domain=com.crashlytics.mac.error-domain.process-dsym Code=4 This version of OSX is not able to perform the necessary dSYM transformations. UserInfo={NSLocalizedFailureReason=This version of OSX is not able to perform the necessary dSYM transformations.}

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

There's no information anywhere about this .symbols files and the information that they contain. Can they be used to symbolicate a crash (if DSYMs are not available)? what format do these files have? Using strings over a .symbols file, I can see that they do contain symbol names, but the file is not supported by any of the usual tools (dwarfdump, otool...)

after download the artifact. show in finder: extract the file right click then select show package content right click at folder dSYM, select compress you can upload the zip

Thank you for sharing your post. Please be advised that Xcode 26 is currently in beta testing. Could you please provide the beta and build number you are using, as well as the version of macOS you are running? To ensure the comprehensiveness of your report, please include the build number at which you initially encountered the issue, as well as any relevant screenshots, recordings, and dSYM file. Additionally, creating a test project can be a helpful way to demonstrate the issue to this problem. Before submitting a bug report, please provide additional information, including the nature of the project you are working on and any specific details that would be crucial for reproducing the issue. If you have a sample project showing this issue I can test with, please share. Do you get the same results with just the relevant code in a small test project? If so, please share a link to your test project. That'll help us better understand what's going on. If you're not familiar with preparing a test project,

I have also faced same issue while downloading the dSYM. I have found my dSYM under TestFlight build section. Check my post here - https://stackoverflow.com/questions/65210768/from-where-i-need-to-download-the-dsym-from-app-store-connect

Is this in C++ files? There are some known issues that make address to source line attribution...problematic.If it is code you are willing to share (or write a smaller example of), you could file a radar and attach the project, the compiled binary, dSYM, and Instruments trace, along with a description of the problematic source files.

Are you actually missing a dSYM in the .xcarchive, or are you saying that it's missing only in the .ipa you upload? Xcode won't include the dSYM in the upload when bitcode is enabled, because it has no use. The bitcode compilation process will create a new dSYM for you as a byproduct of any compilation, which you download later in the Xcode Organizer, and it is this new dSYM that helps you debug crashes coming in from customers who download your app from the App Store.