dsym file

In general this should not be necessary as Instruments uses Spotlight to locate your dSYMs. So as long as you don't build your projects into a location Spotlight cannot see, this should all just work automatically.You can test this by profling your app from Xcode and taking a short recording. Then go to File->Symbols..., and look for your binary/library that is missing symbols. Copy it's UUID (it looks like XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX).At a terminal run mdfind XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX (with your UUID pasted there instead)If Spotlight locates the dSYM in your build folder, then Instruments should be able to see it as well. If the file isn't listed, then Spotlight can't find the file. Either Spotlight isn't indexing that location, hasn't indexed it yet (maybe you just installed a large number of files), or perhaps you need to rebuild your Spotlight index (sudo mdutil -E /).If Spotlight locates your dsym but Instruments cannot

When in doubt, please file a radar with a reproducible test case. Here, that would mean attaching a sample project, the saved Instruments trace, and the application binary and dSYM.

I am also having this issue.This seems like a big oversight that you can only get dSYMs if uploading to the app store.If I go to the archive in the finder, I can get the dSYMs for the frameworks that my application uses but not the dSYM for the application itself.

Same situation here. All archives built with dSYM/DWARF and in our case no bitcode. Yes, I know we can retrieve it from the local archive file when no Bitcode is used.

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

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

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