Pushing an App - how do I access the .IPA file?

pulseblue 8 years ago updated by icahill (Administrator) 8 years ago 5
On the Select Your Build Type page, it says "You will receive an .IPA file to submit to the App Store."

Is this via email?

If I choose the other option, "Live update", is there a fee for every update that I want to release?
In order to retrieve an IPA file, you must follow the steps to set up an Apple Developer Account. Once that is complete, you will need to create a distribution provisioning profile as well as a distribution certificate which you will use to make a .p12 file that will contain your cert and a private key.

Here is a short video on how this is done: https://vimeo.com/41295380

Once you upload the p12 and your provisioning profile to the studio, then you will be able to make IPA builds. Upon a successful build, you will be taken to the Build Logs tab and the build will be available for download directly from the studio.

Live Updates are a good way to push content to your App instantly, making a build with this option will not produce an IPA, but will send the update through the CMS. You are still required to have your certs set-up though.

Currently in Beta a live update is free, but once we come out of beta it will be part of the $250/month plan.
Thanks Ian

But the ad-hoc build is just for testing, right? How do I download an IPA ready for submission to the App Store?

When I go to General > Version History, I can see a number of items in there, including these types: Ad-Hoc Build, Live Update and Built for Store.

One of them is tagged as active_1.0, and all the others have 'promote' button next to them. What does the 'active_1.0' refer to, and isn't this where I would download the IPA from?
You will go through the same process for a store build, only you create a provisioning profile that matches your p12 for a build not adhoc. These you will upload at the bottom of the Apps setting page rather than the Ad-Hoc page.

IPAs should display in the Build Log, what you are seeing is version history for the App project. Anytime you attempt to make a build either from the Ad-Hoc section or the Publish button it will show up in Version History.

It is very important that you create you p12 correctly, it can be used for both adhoc and build, but your provisioning profiles are unique and have to match with the distribution cert you made your p12 file with.
Thanks for that, that was my problem I think - I'd created two different p12's and two certs from different profiles. Defintely a confusing process the first time around!!

By the way, really enjoying learning my way around Rarewire - it's a great App, and fun to use!
Great to hear! Let me know if you need any more help.