Databases
StackOverflow2013
Postsdbo
POiOS Static Library Debug Symbols not being in included in dSYM
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POiOS Static Library Debug Symbols not being in included in dSYM
    text
    copied!<p>I'm working on a series of iOS apps which will share a common codebase. I've developed the common codebase as a static library and want it's debug symbols included in the primary app's .dSYM file. My understanding is that this is possible, but I have not gotten it working yet.</p> <p>The common codebase in its own project which has a static library as a target. This project is dragged into the primary app's project. In the primary app's target's Build Phases I've added the static library as a Target Dependency and under Link Binary With Libraries. The project builds and runs as desired.</p> <p>Now, if I generate a archive from the main project, I can view that archive in Finder, and it contains a .dSYM file that can be used to symbolicate crash logs. However, the .dSYM only contains symbols for the primary app, not for the static library. To over-confirm this, I ran the following: </p> <p><code>dwarfdump /path/to/app.dSYM</code></p> <p>And the output (mostly) did not contain any symbols from the static library. The only exception I have found is that my primary project's AppDelegate is a subclass of an object in the static library, and there are entries for that super class in the .dSYM. However, none of the other classes are present. </p> <p>In the static library's project's target's Build Settings, I have set the following:</p> <ul> <li>Strip Debug Symbols During Copy: NO</li> <li>Strip Linked Product: NO</li> <li>Generate Debug Symbols: YES</li> <li>Symbols Hidden by Default: NO</li> </ul> <p>If anyone can offer some guidance, I would greatly appreciate it.</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload