Test Flight was introduced in iOS8 and is Apple's preferred distribuition mechanism that allows a developer to share a binary with internal testers (up to 100 devices) and external Beta Test Partners (up to 1000 devices).
The original process was limited to 100 devices, and you would need to gain the UUID's of each device (especially if they are not located near your development machine) and then generate a certificate to include the testers devices, generate the binary and sign it. I would then need to distribute the binary to the testers, along with certificates.
That was limiting, and time consuming, especially if your Beta Test Partners are based in different countries.
The new mechanism mean we don't need to gather the UUIDs and nor are we restricted with a small subset of test partners. It also makes the process very easy for Beta Test Partners to gain access to the latest build of your program/game and download to their device without all the faff of installing certs and adding the binary to their iTunes.
If I use XCode I can distribute my app significantly easier and with little fuss, and have full control.
Unfortunately, I am unable to distribute a Beta test version of my app/game to my iOS testing team via this mechanism which is the Apple standard going forward.
Quote: "Why should TGC spend time adapting this feature?"
It's not development per-se, there is an issue uploading the binary to iTunesConnect as Push Notifications entitlement is set and the certificates are not requested as part of the export, as a result the binary is rejected and can not proceed until resolved. Solution (Take out Push Notifications if we're not using them)
Taking that forward, if I try to release the binary under the new AppStore rules, there is a high probability the binary will be rejected for the same reason.
https://www.facebook.com/WonkyPix
http://www.wonkypix.com
http://www.appstore.com/jsecconsultancyltd