> On Oct 26, 2020, at 10:00 PM, Steven Mills via Cocoa-dev
> <cocoa-dev@lists.apple.com> wrote:
>
>
>> On Oct 26, 2020, at 17:49:59, James Walker via Cocoa-dev
>> <cocoa-dev@lists.apple.com> wrote:
>>
>> I don't see any "Download Debug Symbols" in the Organizer. I don't think it
>> exists for macOS apps.
>>
>> However, one can right-click on an archive and select "Show In Finder", then
>> once in Finder right-click again and Show Package Contents, and drill down
>> to find dSyms. (Usually just one, but if your app builds with a private
>> framework, there could be more.)
>
> Yes, Apple needs to remember when writing docs that not all apps are for
> mobile! I have to refer to that doc every time I get a user crashlog, once or
> twice a year, and it always take the same amount of time to figure out what
> they're talking about. I really hope they make this a more automatic feature
> in Xcode: Open the project, open a crashlog, choose a menu item to
> symbolicate, and let Xcode do the confusing part about loading the dsym from
> the archives.
While I agree this would be a good thing to have, I don’t see how Xcode
could find the dSYM to use given that they are typically ephemeral. The dSYM
is tied to the build. So if you build your project twice you will have two
different dSYMs. Only the dSYM for the build that generated the crash log file
will be able to symbolicate it. So, if you want to symbolicate your crash logs
you need to save your dSYM files & resulting app bundle somewhere for each
build of your app you publish. Then you can use them to symbolicate user logs.
What Xcode could do, however, is (given a path to a directory
containing all the dSYMs for your published builds) parse the log to figure out
which dSYM/app bundle pair in the directory to use (probably based on build
info and/or version) and symbolicate. You would also need to take the
additional step of properly updating these values in your project for each
published build.
Either way, that sounds like a reasonable request to make. You should
write up a bug report and send it to Apple.
—Rob
> _______________________________________________
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/petrock%40mac.com
>
> This email sent to petr...@mac.com
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
