dsym file

You should look inside the Xcode archive to see what the final built app looks like. By that I mean the innards of the .xcarchive in the Organizer, rather than the contents of the .xcframework package. There, I'd first validate what you see on disk inside the app's Frameworks folder, and then I'd also do the same for the dSYM folder. Since you're expecting a static framework, there shouldn't be a binary inside the frameworks folder, but you should confirm there isn't, and then also see what's in the dSYM folder. — Ed Ford,  DTS Engineer

I can not symbolicate the crash logs because the UUIDs in crash logs and dSYM (extracted from my local xcarchive file) don't match. I can't figure out why the mistach happened. In the end, I deleted two builds listed in app connect webpage (I am confused about which was the one submited and rejected), and rebuild my archive, upload, and submit once more. Now I am waiting and then decide the next action when Apple's review result comes. Beside, I found no way to download my xcarchive file previously uploaded.

Guys same for me apparently for some builds downloading of dSYMs isn't available anymore, any hint what could lead to this? Bug on Apple's side?

That's a bit strange, normally it's the other way around, dSYM being included in release build and not in debug. Check your schemes and make sure Archive is using Release config. Then under your project's build settings select All and Levels instead of Combined. Make sure DWARF with dSYM is selected for your release builds and that Strip Debug Symbols During Copy is set to No. Is your project relatively new? Does it have an Info.plist?

I've gotten it to work by deleting the folder $HOME/Library/Developer/Xcode/Products/<bundle.id>then clicking download dSYMs... in organizer, and restarting Xcode.

Thanks for the reply. Is there no way to do this without generating dSYMs? That process significantly slows build time in our project. It would be great do be able to rely purely on DWARF for this.

Same here, since the new “Ready for Submit” status release, some of our builds randomly didn’t get the Download dSYM link, even with including symbols…

I duplicated your radar issue: 26536862 as issue: 27171672. iTunes Connect states the dSYM includes symbols, but both Xcode crash reporter and Crashlytics hide my code.

I can download the dsyms now, but I see no stack:LocalCast: NO_CRASH_STACK + 0or for another crash I see a stack trace which looks like this:Localcast: 0x1000a4000

Yesterday I wrote to support as suggested in Apple Staff comment. Today I found desired Download dSYMs button inside the build that we uploaded to appstore also yesterday.

As QuinceyMorris points out, the debugger has the advantage of running against a debug build, which has all the information it needs contained within the binary. Instruments almost always is run against a release build, which does not contain that information. Instead, Instruments must rely on the dSYM for both symbol and source level information.I can't speak to the issues developers may be having generating dSYMs, but if those problems are affecting your workflow it's worth a radar against Xcode to see if we can remove this pain point.

I'm seeing the same issues with my tvOS app. Shows crashes but cannot symboilcate any of them. I've tried downloading the dSYMs in the organizer but that doesn't help.

Having the same issue at the moment. Not sure what's happening there, since this is not a new app and been on the store for a while...Suggestions?Edit:A workaround that helped me was as follows:- Log into iTunes Connect and go to My Apps- Click on the app that you're trying to download the dSYM for- Go to 'Activity' tab- Click on the version you want to expand it and show all the uploaded builds- Click the build you wantYou'll be shown details about that build, and the option to download dSYM in the bottom right corner under 'Includes Symbols' header