When you use a mergeable framework in your app, you still need to embed the framework so that you get all of its resources. However, what gets embedded is a cut down framework, with all the resources but only a stub Mach-O image.
Interesting! That explains a lot and was not clear to me at all. (Also it does not seem to be documented anywhere?)
In the beginning I analyzed the app bundle to find out if this feature really works as expected and just assumed that something was wrong because I expected that:
The resources are part of the framework in "ReexportedBinaries" folder in debug builds (which they are not)
The whole merged ".framework" folder should not exist at all in release builds (which it does)
Then I thought maybe I should stop embedding merged frameworks and tried that.
And everything worked great - in Simulator.
And then I tried on device - and it crashed I was totally confused.
And there's also this issue, which made me think this whole feature is just horribly broken.
But apparently it's just very complex and under-documented.
Do you happen to know how to find out if a framework is just a "cut down framework" that really is merged into the app binary or not (to make really sure everything is configured correctly)?
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags: