Lets suppose that:
- XCode4 is used to "Archive" a project and generate an app.ipa file that has been signed with an Ad-Hoc profile
- The Ad-Hoc profile is aware of 10 distinct iOS devices. This means that the app.ipa can be pushed to 10 folks for testing
- Now if an eleventh (11th) device is added to the Ad-Hoc profile via the apple portal, then we end up with an updated profile!
Given that:
- we do NOT want to create a new "Archive" using XCode because a lot of code has changed
- we simply want the comfort of taking the exact same app.ipa file and re-signing it with the update profile so that we may start sending the app to the 11th device in an ad-hoc manner as well.
What can be done to accomplish this?
- Please do NOT suggest using the repository to check-out the earlier version of the code and then using archive with the updated profile. I am already aware of that workaround and I want an option that is much more technologically comfortable than that
UPDATE:
Thanks to this blog: http://blog.futureshock-ed.com/xcode-ad-hock-provisioning-certificate-pains
I figured out that I can simply open the Organizer in my XCode 4, select any one of the previously archived builds and when I look to generate the app.ipa again, it will use the newly imported & updated adhoc provisioning profile to create the ipa file.
How to import the updated provisioning profile before doing this action you ask? Well just double-click the newly downloaded profile and make sure to delete its older sibling in the window that pops-up to show both of them now sitting on your mac. You can determine which one is the older by visually inspecting the value for "Creation Date"
It should have been obvious but somehow it wasn't, I wonder how many others suffer from the same affliction.