IOS sends xcarchive files to customers (in Grooming)

<span id="Label3"></p><p><p>For security reasons, the customer will not distribution the App's provisioning profile to the developer, but can give a development provisioning Profile. In this case, we set the release version of provisioning profile in code signing to development provisioning profile, and then we can do Archive. Then send the archive to the customer, he can be organizer for subsequent release operations.</p></p><p><p>This mainly involves the knowledge of archive and Distribution.</p></p><p><p>Archive provisioning profile does not do too much testing, only need to meet the minimum requirements can be: to be able to run the real machine STANDARDS. so, even a setting like this can be archive smoothly:</p></p><p><p></p></p><p><p>To prove it, here is the final step of the export Ipa:</p></p><p><p></p></p><p><p>This use of development provisioning profile of the export operation, I feel is not really distribution.</p></p><p><p>Let's look at several ways to publish in organization:</p></p><p><p></p></p><p><p>We just used the fourth option, just development provisioning profile, but the first 3 each needed a different type of distribution provisioning Profile.</p></p><p><p>The fourth option is more likely to be confused, what is called development distribution?</p></p><p><p></p></p><p><p></p></p><p><p>note, do not confuse archive and distribution, the real distribution is carried out in Organizer. Archive Bundle ID is critical when the bundle ID is determined and must be selected by the corresponding certificate team to Publish. and organizer will be in the distribution process according to this ID to find matching provisioning profile, if there is a corresponding provisioning profile can be released!</p></p><p><p>IOS sends xcarchive files to customers (in Grooming)</p></p></span>