Search results for

dsym file

75,572 results found

Post

Replies

Boosts

Views

Activity

Reply to Instruments/Allocations inconsistent object counts when drilling down
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.
May ’16
Reply to Download dSYMs fails with Missing App Record
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
Oct ’17
Reply to How include dSYM when I build my Framework project?
How can this be done without having the framework project within the app project? In m case I have an Xcode iOS project with type framework. Then I create a .xcframework and include that into another project with type app. In both projects the debug information format is set to Dwarf with dSYM in release build. Within the app project, within the Frameworks, Libraries & Embedded content section the framework is set to Embed and Sign, and its within the Embed Frameworks section. Yet when an archive of the app is created there is no dSYM present from the framework.
Apr ’25
Reply to GPU Frame Capture
Hi Seth-Thanks for the note (didn't get a notification that there were any responses or would have replied sooner). it is currently DWARF w/Dsym. Something to note.. the GL calls are in a statically linked library (which we maintain) and it's also set to DWARF w/Dsym. The configuration is that the library is a project in the workspace and is a dependency of the main project, so all the source is available and the entire codebase is built each time, but technically the draw calls are being made in a library. The library is all in C++.Is there something about that config that woudl cause the issue?Thank you!
Topic: Graphics & Games SubTopic: General Tags:
Nov ’15
Reply to Xcode 26 increase in dSYM size
Currently on Xcode 26.0 beta 7 (17A5305k), macOS 15.6.1 (24G90) For our main Phonepe app (https://apps.apple.com/in/app/phonepe-secure-payments-app/id1170055821) dSYM size went from 281 MB (xcode-16) to 584 MB (xcode-26) Tried replicating the issue for Alamofire Example app (https://github.com/Alamofire/Alamofire), there as well dSYM size went from 2.7 MB (xcode-16) to 5.8 MB (xcode-26). All Build were all release builds
Sep ’25
Reply to Lots of warnings when building with Xcode 7 with 3rd party libraries
I created a new project in Xcode 6 and a new project in Xcode 7 and compared the .project files. It looks like the Debug Information Format default has been changed from Xcode 6 to Xcode 7, but any project that originated from Xcode 6 would still have this turned on.Xcode 6:DEBUG_INFORMATION_FORMAT = dwarf-with-dsym;Xcode 7:DEBUG_INFORMATION_FORMAT = dwarf;This is found in Build Settings -> Build Options -> Debug Information Format as mentioned above. Just wanted to give some more insight into this.
Sep ’15
Reply to Xcode Cloud / Crashlytics no longer processing dSYMs
If you take a look at the artifacts created after a successful build, there would be a crash log created with the latest macOS version. Upon opening it, the upload symbols functionality has a crash, which in turn causes the issue of not pushing the dsym. I too was facing this while using XCode cloud with macOS Version 14. Try downgrading macOS version to 13. This worked for me. With macOS version 13 I still get the crash log file but this time its different but crashlytics works as expected.
Oct ’23