Question

I have developed an iOS app. I want to give it for third party testing. What should i choose scheme when creating build for third party testing, Debug or Release? Third party testing device UDID is included in the provisioning profile. If I use TestFlight for OTA installation, will the UDID to be included still? (or) TestFlight app doesn't need any UDID included in the build?

Please advise!

Thank you!

Was it helpful?

Solution 2

Archive your app, which will be a release build by default as far as I know. Doesn't really matter what the build type is, then in the archive manager click "distribute" and "save for enterprise or ad-hoc deployment", and select a provisioning profile for the app that has your beta tester's device IDs embedded in it, only those devices will be able to run the app.

This will create a file with the profile built in. Users can install it on their phone using three methods:

  • add it to their iTunes library and sync the phone using USB
  • use the "iPhone Configuration Utility", which is a free download for windows/mac from Apple's website, and doesn't require iTunes and all the baggage that brings along with it
  • upload the file to a website and also upload an XML file pointing to the download URL and also a PNG image, display name, and a few other things. Get the iOS device to visit the XML file's URL with itms-services:// as the protocol. Any means to open the URL is fine, email, website link, SMS message, whatever.

Test Flight uses the third approach. But you can easily set it up yourself.

Extensive documentation for all three approaches is available at http://developer.apple.com

OTHER TIPS

(Seems like I can't comment yet). In response to the comments posted to the original question:

TestFlight, part of Burstly, is now Apple propery, as mentioned in this rumor http://www.macrumors.com/2014/02/21/apple-may-acquire-testflight/

and later confirmed by Apple. http://recode.net/2014/02/21/apple-confirms-burstly-buy/

As mentioned by someone, Apple uses shuts down their acquisitions and hence it may not be a very good idea to start using it now.

Whichever method you use you'll need to build the app with a provisioning profile that includes your tester's device UDID.

I suggest using a Release build, so they are actually going to be testing the same version you are planning on releasing.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top