dsym file

I am having this issue too. When I check the newly generated Archive's folder, I can only see the folders BCSymbolMaps, Products, and dSYMs, whereas previous (and working) archives had those three, as well as the Info.plist and the folders SCMBlueprint and SwiftSupport. This happened to me after updating Xcode. I have tried all previously mentioned solutions (to my knowledge). Any help is welcome.

I get the same annoying warnings since Xcode 16. Currently seeing them under 16.1. Not only do I see it in scripts being executed as an Xcode Archive post action, but also in other scripts on my compputer. Don't know if it is related, but since then DSYM info for Sentry is also broken. Path is: /Applications/Xcode.app/Contents/Developer

For those who (like me) stumbled upon this thread trying to create an XCFramework with debug symbols & bitcode, I've made a build-phase script that makes it easy to implement. Create a new target for your framework that is just for creating the .xcframework container (this is needed because when running this script on the same target, it gets an infinite loop) Add the script to the target's Build phases --> Add new run script For the rest, see the comments in the script Set the output folder var UNIVERSAL_OUTPUTFOLDER=${BUILD_DIR}/${CONFIGURATION}-universal To make an XCFramework, we first build the framework for every type seperately echo XCFramework: Starting script to build an XCFramework. Output dir: ${UNIVERSAL_OUTPUTFOLDER} Device slice. echo XCFramework: Archiving DEVICE type... xcodebuild archive -scheme ${PROJECT_NAME} -configuration Release -destination 'generic/platform=iOS' -archivePath ${BUILD_DIR}/archives/${PROJECT_NAME}.framework-iphoneos.xcarchive SKIP_INSTALL=NO echo XCFramework: Arch

Similar problem happening here. Symbols and Bitcode uploaded for the latest version of our app, as confirmed by iTunes Connect.Downloading dSYMs works fine, but they are useless, filled with __hidden#xx symbolication descriptions, despite symbols having been included.So, the crash reports symbolicate, but there is nothing to be learned from them.Filed as another radar issue: 26536862

On manually integrating the framework and running the command image list MOCore the output is id /Users/rakshitha/Library/Developer/Xcode/DerivedData/swifttesting-cnvmmbfljmnratdcgnfpynlryijy/Build/Products/Debug-iphonesimulator/swifttesting.app/Frameworks/MOCore.framework/MOCore/System/Volumes/Data/Users/rakshitha/Documents/MoEngage-iPhone-SDK/MoEFramework/MoEngage/XCFramework/MOCore.xcframework/ios-arm64_i386_x86_64-simulator/dSYMs/MOCore.framework.dSYM/Contents/Resources/DWARF/MOCore Where the framework resides in the path /Users/rakshitha/Documents/MoEngage-iPhone-SDK/MoEFramework/MoEngage/XCFramework/MOCore.xcframework/ios-arm64_i386_x86_64-simulator/dSYMs/MOCore.framework.dSYM/Contents/Resources/DWARF/MOCore Find the attachment below for the output of the swift-healthcheck command. (The attachment has partial output only due to size restriction) swift-healthcheck Looking forward for your assistance

@manumayank The best way I have found is to use grep on an archive version. Is that the instructions you got? Open /Applications/Utilities/Terminal Type the following on the command-line to change to the directory where the application binary is: cd ~/Library/Developer/Xcode/Archives// For example, cd ~/Library/Developer/Xcode/Archives/2020-03-09/SampleApp 3-9-20, 11.47 AM.xcarchive To search for open_dprotected_np, type the following on the command-line: grep -R open_dprotected_np * should provide you a result like: Binary file dSYMs/SampleApp.app.dSYM/Contents/Resources/DWARF/SampleApp matches To point you into the right direction. Do you have any result? Albert Pascual
  Worldwide Developer Relations.

It seems that sentry-cli has changed since the previous responses were made. Here's the ci_scripts/ci_post_xcodebuild.sh that worked for me: set -e if [ ! -d $CI_ARCHIVE_PATH ]; then echo Archive does not exist, skipping Sentry upload exit 0 fi # This is necessary in order to have sentry-cli # install locally into the current directory export INSTALL_DIR=$PWD if [[ $(command -v sentry-cli) == ]]; then echo Installing Sentry CLI curl -sL https://sentry.io/get-cli/ | bash fi echo Authenticate to Sentry sentry-cli login --auth-token $SENTRY_AUTH_TOKEN echo Uploading dSYM to Sentry sentry-cli debug-files upload -o -p $CI_ARCHIVE_PATH

Is the .dSYM baggage needed to get to the proper line numbers or something?Yes. Because there are enough other factors involved (compiler versions, optimization settings, etc.) that the translation from addresses inside a method to line numbers wouldn't be deterministic without a symbol map.You can find documentation for dSym and the related stuff on the LLVM pages, but I don't know whether that's We're documenting this after figuring it out or being told what it is, so we know what the heck we're doing in the future, We're making this up, or a combination of the two. As software, it's probably a bit of both. 🙂lldb.llvm.org/symbols.htmlEdit: When dealing with debugging, do also keep in mind that there's an option to strip debugging symbols from executables. So were you running nm on the binary with debugging symbols; or with only the necessary symbols needed to interact with the Objective-C runtime, linker, and loader?

+1. It started happening randomly around February 3 (JST), and since February 8 (JST), none of the builds have generated dSYM!I had to increment a lot of build versions to try this out... I had to reorganize my version control... (I had to patch the marketing version or something, even though it wasn't a patch for the app)

You need make sure that the binary UUID in the crash report matches the UUID in your .dSYM and that UUID is visible to Spotlight. To learn more, read this post. Share and Enjoy — Quinn “The Eskimo!” Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Hello once again, sorry for disturbance, begging for a help.Could you please help me to symbolicate crash report, spent the whole day, suppose I'm doing something wrong.Tried it with atos, but with no luck(xcode gives nothing at all. Organaizer even doesn't download .dsym file.You my last resort.Really appreciate your help and responsiveness.Thanx in advance

Me too.We have the same issue. We have a project that mixes Obj-C and swift and uses Obj-c and swift frameworks.I hope that this issue will be soon fixed by Apple. We found a workaround to generate a development IPA:- Archive in Xcode 10 by disabling dsym for release in project settings- Export the IPA with Xcode 9

@eskimo I followed your steps and I am able to find my workspace path as well. I am working on this issue as well due to security reasons and I have found that disabling bitcode during export process is limiting this issue somehow, but disabling bitcode is not necessarily what I want to do because of dsym, analytics and other advantages of bitcode being enabled. Do you have any solutions to this problem?

I'm seeing a similar issue. Xcode consumes all available system memory and the then machine freezes and needs to be rebooted. Have you found any workaround besides just disabling dSYMs? FWIW, choice of legacy vs new build system does not affect the issue for me, nor does cleaning the project or deleting all of the build intermediates.