dsym file

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.

I also have the same issue - nothing has changed about our Fastlane build process, but recent builds aren't showing up with the download dSYM link in ASC. We have started signing and uploading multiple builds for the same binary (with different build numbers for TestFlight vs. App Store release) - a previous poster mentioned something similar. Could that be the problem?

That's a great question for Hermes to answer. I see that it's an open source library, but getting a dSYM for their library may mean you need to build it from source (if you're using a pre-compiled version) or that you'll need to alter the build configuration they use. Their support will be in the most knowledgable position to answer those questions. — Ed Ford,  DTS Engineer

I get the same error. I'm not using any third party frameworks or static libraries. I have my project set to include DWARF with dSYM in the build and debugger. This is a MacOS C/Objective C XCode project. With some Swift. Most of the discussion about this for iOS projects. When I verify or upload my App I just ignore this. Is this OK? Is this an Apple bug?

It is the log, but it is not symbolicated. If it were, the lines1 usagApp 0x000000010015724c 0x1000c0000 + 619084 2 usagApp 0x000000010014ba80 0x1000c0000 + 572032 3 usagApp 0x000000010014b9c4 0x1000c0000 + 571844would contain useful information: the exact file and line numbers in your code where the crash occurred. Without that, there's not much anyone can help with.If Xcode won't symbolicate it when you view the log in Devices -> Device Logs, then you have an uphill task. Some people have reported that the build UUID doesn't match for some reason and have had success editing the log with the correct UUID to match the correct DSYM from your app archive... it's not for the faint of heart though. From what I've read there's no one size fits all solution to fix symbolication problems.

I am also having the same issue (Your user account is attached to several iTunes providers. Create separate accounts for each provider before logging in.) when trying to download a dSYM file.It does *sound* like a roles issue. Strangely enough, I was able to switch between two different itunes groups that my developer id is associated with. Maybe thats what is meant by iTunes providers.

Just to bring this up to date as of Xcode 12.2, Apple is allowing Xcode to download the symbols. 1) Go to the Organizer and find the app you uploaded to the store. 2) Click the Download Debug Symbols button beneath Details. 3) Right-click the app and Show In Finder. 4) Right-click the xcarchive and Show Package Contents 5) Your dSYMs are in the folder...