Why do public titles create so many products?

When archiving my current iOS project, I ran into a problem of several products .

Basically, this happens when Xcode cannot recognize your project as a single product and, therefore, cannot present it as an iOS application archive that you send to the App Store.

In my case, the workaround removed all Public headers from some reference static libraries (changing them to Project headers),

This is bad because these headers must be publicly available for some reason.

Why is this necessary? Is this an Xcode bug or am I missing something? Why do some static libraries need this and some not?

And finally, is there any other way to solve this problem that does not require changing the visibility of the header?

+6
source share
1 answer

Did you see the answer you wrote yourself?

Ok, answering my question. It turns out that this is a problem with dependent projects in Xcode 4. If this happens to you, look at the build options for all your dependent projects (for example, static libraries) and make sure that the option “Skip installation” in the “Deployment” section is set to YES.

More details here: http://flakasoft.com/developer-tips/xcode-4-bug-solution-for-archiving-build-with-static-library/

0
source

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


All Articles