“The first significant change is TestFlight will not require developers or testers to deal with UDIDs or provisioning profiles,” Arnott reports. “Currently, in order to add a new device, the flow goes like this: 1. Developer asks tester for UDID (and has to provide instructions on how to retrieve it if the tester doesn’t know how) 2. Tester uses an application to retrieve the UDID 3. Tester sends UDID to developer 4. Developer logs into Apple’s Developer Portal 5. Developer adds the tester’s device to the account 6. Developer adds the new device to the appropriate provisioning profile 7. Developer updates app with new profile 8. Developer distributes app to tester.”
Arnott reports, “The exact flow may differ depending on what tools a developer is using, but that’s more or less how it works. TestFlight’s flow looks like it’s going to be more like this: 1. Tester tells developer their Apple ID 2. Developer logs in to iTunes Connect 3. Developer sends email invitation to tester 4. Tester accepts invitation 5. Tester installs app via TestFlight app.”
Much more in the full article here.
MacDailyNews Note: Our developer Empirical Development used TestFlight for the current (v.3.1) version our MacDailyNews app prior to Apple’s acquisition and it was a joy for us to test each beta as our app progressed vs. dealing with the previous UDIDs/provisioning mess.
[Thanks to MacDailyNews Reader “Dan K.” for the heads up.]
Apple acquires Burstly app testing and advertising company – February 21, 2014