On Oct 27, 2020, at 00:54:40, Rob Petrovec <petr...@mac.com> wrote: > > 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.
Yes, it would do the same thing that the doc tells us as humans to do, but it could do it much more efficiently and speedily. It can easily find the correct archive, as long as you're a good developer and don't throw out your official build archives. -- Steve Mills Drummer, Mac geek _______________________________________________ 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
