Xcode 4: Is the profiling profile of the assembly archive defined?

Question

I did not use the archive function in Xcode 3, but now I'm used to it in Xcode 4. Until now, I always had three or four build parameters in all my projects: Debug, Distribution AdHoc and Distribution AppStore, Distr. AdHoc and AppStore were both “Release” instances and only differed with respect to their training profile chosen for Codesigning (so that, in fact, they were convenient, so I never sent the wrong person the wrongly signed assembly).

Now I noticed that Xcode is asking me which profile I would like to sign my assembly with whenever I export the archived organizer assembly form, but at the same time, the assembly will also fail if the selected provisioning profile in the assembly settings is invalid. Regardless of the Xcode 4 archive backup profile, or are you tied to a provisioning profile? How do you solve the build problem for AdHoc and AppStore without having too many build settings groups (switching groups related to build schemes has become quite cumbersome in Xcode 4)?

Thanks!

Answer 1

in Xcode 4, if you archive the application that it is signed with the provisioning profile that you specified for use in its build configuration. Most likely, the settings migrated from the Xcode 3 project.

An archived application can be written off with a different condition profile later (although the organizer or command line), so in a sense, yes, they do not depend on the provisioning profile.

Two building management offers for AdHoc and AppStore:

1) The first uses Xcode 4 schemes and creates new schemes for AdHoc and AppStore

In the "Schema" menu: "Edit Scheme" → "Duplicate Scheme", then in the archive you can select the desired assembly configuration (AdHoc, AppStore, etc.), you can call this scheme AdHoc, AppStore, also suitable. When you want to create for release, simply select the target scheme and it will sign it with the appropriate provisioning profile from the assembly configuration.

2) Save 1 scheme, remove code signing from your build configurations and sign applications only with the help of the organizer after archiving.