All geek questions in one place

Can I still symbolize the distribution assembly that stripped it of debugging symbols?

In fact, I have two related questions:

  • If I want to be able to symbolize the failure logs from the assembly assembly (that is, the assembly that I gave to someone to beta test my application, and not the one that is already in the appstore), I should disable the "Strip Linked Product" and "Strip Debug Symbols During Copy" for debugging or for release ? In fact, can this cause any problem - will I disable them both forever (even in my appstore view)?

  • If I distributed the assembly to a beta tester, but it had the "Strip Linked Product" and "Strip Debug Symbols During Copy" options enabled , is there another way to symbolize their crash logs?

+6
source share
2 answers

When you create an archive (assembly> Archive), the archive will contain a folder named dSYMS that contains dSYM files (a debugging symbol file) for your application and other related libraries. This means that you can separate debugging symbols from your products, but save dSYM files to indicate dSYM reports. This post has more information on how to use the atos tool to indicate a crash report, provided you have application files and dSYM .

In general, Debug assemblies contain Strip Debug Symbols When Copy set to NO , and in release versions it is set to YES to reduce binary size.

+3
source

If you distributed your application through the build → archive, you will have a dSYM file associated with it. Now that you get a crash report, there is no need to do anything. Drag the crash report into Xcode and it will automatically be added to the Organizer section. If a valid archive and dSYM file are available, Xcode automatically symbolizes the crash log for you.

+2
source

Source: https://habr.com/ru/post/959021/

More articles:


All Articles