Database Reference
In-Depth Information
Figure 7-4. Creating an Ad Hoc profile
The first time through, this isn't so bad. But what happens the next time someone wants
to add a device? You need to go back to the portal, add the devices, add the devices to
the profile, regenerate the profile, download the profile and install it in your keychain,
edit the application, and select the new version of the profile in the Ad Hoc configu-
ration as the code signing identity, rearchive the app, and distribute it. And then, prob-
ably, pour yourself a stiff drink. Now imagine doing that a couple of times a week!
One way I try to avoid some of the madness is to insist that new device additions be
bundled up in groups, so that I can add 5 or 10 at a time rather than in onesie-twosies.
Of course, if the VP of sales needs to be added so that he can give a demo, you'll probably
have to bend your policy. Another way you can spare yourself some pain is to incor-
porate the creation of an Ad Hoc image into your automated build processes. The magic
command you need to add to the build is:
/usr/bin/xcrun -sdk iphoneos PackageApplication \
-v appfile -o ipafile --embed mobileprovisionfile
So, for example, the Buggy Whip folks might say (assuming that the app file was in the
build folder, the profile in the certs folder, and that the resulting .ipa file should be
placed in the dist folder):
 
Search WWH ::




Custom Search