I am attempting to create an archive .ipa for distribution via testflight. The archive creates, and I choose export, then choose ad hoc, then select my team. However, at this point I get the below screen.
I know that my certificate is valid, as I created an .ipa in xcode 5 with a different provisioning profile about 2 hours before I downloaded xcode 6 GM. I also know that my provisioning profile is valid and connected to said certificate.
Thing is, in xcode 5 it didn't ask for a team; it only asked for a provisioning profile. Now, export asks for a team, which I provide. Also, of course I have a valid iOS Distribution certificate. I'm using it in the build settings to sign my application. Seems like a strange error to get
Any help would be greatly appreciated.
First of all understand that the error message is a BS repurposed message and not accurate to what is happening here. It's not your fault you have wasted so much time on this. This is an example of 1 small flaw in Apple's workflow costing hundreds of thousands of dollars in wasted developer time. But what can we do?
This is technically the same idea as @steventnorris. I wanted to be more clear because I failed recognize and implement his answer. I had to discover this on my own through much trial and error.
Using a development certificate, I was unable to generate an .ipa. However, using a distribution certificate for ad hoc, I could generate an .ipa. I'm assuming this is either a new 'feature' or a bug in Xcode 6 that requires ad hoc to have a distribution certificate and profile to deploy via ad hoc.
The only way I could generate the AdHoc build (without getting rid of my certificates) was using the command line tool xcbuild as described here:
https://stackoverflow.com/a/25979784/2008167
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With