dsym file

I'm getting a similar error when validating my package after upgrading to Xcode 16. Error: Upload Symbols Failed The archive did not include a dSYM for the LofeltHaptics.framework with the UUIDs [8274DE6D-513B-3DDA-BE9F-C6106B01CB0D]. Ensure that the archive's dSYM folder includes a DWARF file for LofeltHaptics.framework with the expected UUIDs.

It is challenging to pinpoint the exact issue without additional information about your project or a specific project demonstrating the problem. Could you please provide details about your framework or the third-party framework you are using? How was it built, and what are the configuration and settings in the project? A comprehensive view is always beneficial, but I will attempt to offer some potential solutions. However, providing a project illustrating the issue would be more advantageous for such types of errors. The error message indicates that there are two issues with the archive being uploaded to App Store Connect: Invalid Executable: The executable AppInvokeSDK.framework contains Bitcode. App Store Connect does not allow frameworks that contain Bitcode. Bitcode is a way of compiling Swift and Objective-C code into an intermediate format that can be optimized later by Apple's servers. Missing dSYM for AppInvokeSDK.framework: The archive did not include a dSYM for AppInvokeSDK.framewo

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.