We’re using UCB for our iOS builds, but we have an annoying issue that we’d like to get fixed (i wonder if other devs haven’t faced this issue before).
I have imported 2 provisioning profiles into UCB - one for Ad Hoc builds and another for Distribution (AppStore).
Our testers use Ad hoc builds, but the issue is when we want to move to production (and prepare a build for the app store).
If we sign a build with the App store provisioning profile, our QA testers cannot directly install that build on their test devices (a warning message is shown in UCB which is OK).
The problem however is that there’s no good way to handle this scenario, other than creating 2 different builds from the same commit (one for ad hoc and one for app store).
Ideally, what we’d like is an option to let the same build spit out 2 different .ipa’s (and .dSyms). The ad hoc build could be sent to QA, and once approved, the matching App store build will be uploaded to the store.
This is similar to the workflow we use when building locally - an ad hoc build is used, and when approved, we “export” a new .ipa from Xcode (from the same build) and upload it.
Please add support for this, or let me know if there’s any good workaround we can apply.