Search results for

dsym file

77,666 results found

Post

Replies

Boosts

Views

Activity

Reply to App upload warnings (never seen before)
Here's another thread with a discussion of this warning. That thread is long, and the number of folks asking about different facets of these messages makes that thread a bit unwieldily, so I want to reiterate one of my answers here for your clarity: This is a new warning in Xcode 16 where if you're missing a dSYM, Xcode lets you know in case you aren't expecting that — this is to reduce scenarios where you won't are able to fully symbolicating frames coming from your app's code in crash reports. In some cases, you may not have a dSYM, such as a closed source library from a vendor, and in those cases, the warning is safe to discard. — Ed Ford,  DTS Engineer
Apr ’25
Instruments/Allocations inconsistent object counts when drilling down
situation: app in stable state, I see 5 CoreImage objects at top level Statistics / Allocation Summarybut when I click the circle-right arrow to drill down, it only shows 2. and the memory usage total is much lessin the drill-down. has anyone seen this? which is correct?see attached.oh well the attacher seems to be broken. also, if anyone at apple is listening, can you modify Instruments to read the debug symbols out of the executable directly?rather than relying on the dSYM files? those dSYM files seem to always get lost or misplaced or deleted during clean/purgeoperations that are often required during Xcode development. if lldb can do it, you can too! if you inherit a project wherethe settings arent right to generate dSYMs, it can take a long time to find out what is wrong and get them to generate. and it seems to varydepending on what version of Xcode the project started on and what Xcode you are using now.
3
0
628
May ’16
Reply to Xcode 12 beta 3 – XCFrameworks and debug symbols
Your build commands have a few mistakes. I made the same simple framework you did (a single Swift struct), and used the following build commands instead. I'm going to format them here with line breaks and indentation for readability. Note that I've set Build Library for Distribution to Yes and Skip Install to No in the framework target's build settings, so they don't appear here. % xcodebuild archive -scheme StructKit -destination generic/platform=iOS -archivePath iOS.xcarchive % xcodebuild archive -scheme StructKit -destination generic/platform=iOS Simulator -archivePath sim.xcarchive % xcodebuild -create-xcframework -framework iOS.xcarchive/Products/Library/Frameworks/StructKit.framework -debug-symbols iOS.xcarchive/dSYMs/StructKit.framework.dSYM -debug-symbols iOS.xcarchive/BCSymbolMaps/<UUID>.bcsymbolmap -framework sim.xcarchive/Products/Library/Frameworks/StructKit.framework -debug-symbols sim.xcarchive/dSYMs/StructKit.framework.dSYM -output StructKit.xcframework I also notice you
Jul ’20