Geek Answers Handbook

Symbolize the crash log when the application name contains an apostrophe and space (deployed application)

I have an application in the app store that is crashing. I tried several solutions on SO to symbolize my application, using Organizer, Terminal and Tools at different times. So far, nothing has acted - the lines in the reports from the methods in my application are never indicated, even if the lines are for Apple methods. Looking back for a while, it seems that this may have something to do with the name of the application, which corresponds to the lines of the "Angie List" - both with an apostrophe and with space. It’s too late to change the name of the application, as it is live in the store. I have not seen a solution anywhere, and I would be judged in the right direction.

+1
source share
1 answer

Usually the name of the application does not matter if there is no error in the script symbolics that I doubt. Have you checked if you have the correct dSYM?

If you scroll through your last crash log, check the 1st line below the Binary Images , it will look like

 0x1000 - 0x24cfff +YourApp armv7 <f6012c517d783486ab53e45d948b92a2> /var/mobile/Applications/A8EC3C1F-44AF-169A-BC0E-FBBC0F04CDF5/YourApp.app/YourApp

f6012c517d783486ab53e45d948b92a2 is the executable file UUID caused by the failure.

You can find the correct dSYM using the terminal as follows:

 mdfind "com_apple_xcode_dsym_uuids == F6012C51-7D78-3486-AB53-E45D948B92A2"

String F6012C51-7D78-3486-AB53-E45D948B92A2 is a string reformatted to uppercase and 8-4-4-4-12 groups. I think this team will not return anything.

If you have dSYM (e.g. in .xcarchive), you can check its UUID in the terminal as follows:

 dwarfdump --uuid YourApp.app.dSYM

If the symbology does not work automatically, you can try to do it manually by following the instructions presented here: iOS crash reports: atos does not work properly

If an application has special characters, such as spaces or an apostrophe, Apple’s default toolbox will not be able to symbolize it. The reason is that the otool tool that is used in the toolchain cannot handle this. No matter how you pass the file name. Therefore, to fix this, you must do the following:

  • Rename the dSYM package and remove all special characters, for example. from My App's.app.dSYM to MyApps.app.dSYM
  • Open the contents inside the package and go to Contents/Resources/DWARF
  • Rename the file there as you did above.

Now try again. The best way to avoid all of this: NEVER use special characters in the name of your application. If you want to change the name that appears on the screen, use CFBundleDisplayName or the corresponding plist entries.

+1
source

More articles:


All Articles