Re: Xcode 5 & making an .ipa file for ad hoc distribution
Re: Xcode 5 & making an .ipa file for ad hoc distribution
- Subject: Re: Xcode 5 & making an .ipa file for ad hoc distribution
- From: Fritz Anderson <email@hidden>
- Date: Fri, 25 Oct 2013 10:57:50 -0500
On 24 Oct 2013, at 5:48 PM, Fritz Anderson <email@hidden> wrote:
> Your signature says I'm taking my life into my hands by quoting you, but I'll brave it.
>
> On 24 Oct 2013, at 3:46 PM, John Spicer <email@hidden> wrote:
>
>> How does one do this with Xcode 5?
>>
>> I follow the steps as outlined, like in Xcode 4.x but, when I hit "Distribute…" I don't get the 3 options (submit to store, save for enterprise ad hoc, export as archive),
>> Instead I get two options: save build products, OR export as Xcode archive.
>
> It should Just Work, so long as you negotiate a labyrinth of rigidly-defined procedures.
>
> Off the top of my head, here's my checklist. I admit I sometimes resort to trial-and-error in the event. But maybe you can use it to double-check what you're doing:
>
> Distribution signing certificate in a keychain Xcode can reach (Login will do). (Low-probability: You don't have more than one certificate installed with the same common name, do you?)
>
> Ad-hoc distribution profile issued against that signature, the application ID, and a subset of your registered devices. This can be done only in the portal.
>
> The profile is installed. You can do it the old-fashioned way — downloading it when the portal offers and dragging the file onto the Xcode Dock icon — or by hitting the refresh button in the "View Details…" list for your team membership (Accounts tab, Preferences). (I think there are propagation delays; you may have to click the button every half-minute or so till the profile name appears.)
>
> There is a PROVISIONING_PROFILE build setting. Select your ad-hoc profile for whatever configuration you're using for ad-hoc. (You all-but-must give ad-hoc builds their own configuration.) As I recall, Xc4 could be left to infer the profile from the bundle ID, but that's kind of nutty.
>
> Set the code-signing identity to Automatic. Let Xcode figure it out from the profile.
>
> Create a build scheme for ad-hoc builds. Set the Archive action to use your ad-hoc configuration, and to reveal in the organizer when done.
>
> Scheme set to the ad-hoc one.
>
> Destination set to (an) iOS Device.
>
> Product > Archive.
>
> Select the most-recent archive from the Archive organizer. (While you're at it, fill in the Comment field for the build.)
>
> Click Distribute…. Assent to all the business with signatures and permissions. (Is the automatically-selected identity correct?) Arrive at the put-file sheet.
>
> What do you see?
The OP writes me off-list to say that he followed my suggestions, and has the same results. He sends me a screenshot of just enough of the method-of-distribution page of the distribution assistant to show that there are only two radio buttons offered:
Save Built Products | Save a copy of the archive's build products.
Export as Xcode Archive | Export the entire Xcode archive of this product.
If I had the project before me, I might be able to tease out what's going on (a distressing amount of my work is done by Braille), but lacking that, I'm out of ideas. I wish I could be of more help.
— F
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden