I'm following the steps laid out in Creating a static framework which states:
When a client links and embeds the framework, Xcode 15 or later omits the main binary from the embedded framework bundle because it’s already statically linked into the client.
Specifically, I'm adding a new framework target to my project, and then changing the Mach-O type in its build settings to Static Library.
What I'm observing when I build (debug or release) is that that the resulting framework folder inside of the app bundle still contains a binary.
Furthermore, upon inspecting strings and symbols in both the main app executable and this library binary, it appears that my strings and symbols do end up in the main executable and not in the library binary.
Does this mean that this binary is just a stub left behind?
Is this intended?
Can I safely delete this binary with a build phase script?