TestFlight task uses app.development instead of app.release

[jjaffeux]

We should follow TestFlight rules : TestFlight follows Apple's beta distribution guidelines which recommends betas to be signed with an Ad Hoc profile.

[jamonholmgren]

👍

[chrisradford]

Am I correct in thinking this would be as simple as changing https://github.com/HipByte/motion-testflight/blob/master/lib/motion/project/testflight.rb#L120 from Rake::Task["archive"].invoke to Rake::Task["archive:distribution"].invoke?

If so, is there a downside to this change?

[paulsturgess]

I just got caught out on this. Lost a few hours trying to figure out why my adhoc distribution provisioning profile just would not work. Kept getting the obscure error:

Invalid Profile: distribution build entitlements must have get-task-allow set to false.

Switched to the development profile and the build uploaded to Testflight straight away!

[chrisradford]

@paulsturgess you could have also set app.entitlements['get-task-allow'] = false which would also solve that issue.

[jamonholmgren]

To make this a little more clear, TestFlight requires that you upload a distribution Ad Hoc build.

1. Under the Product menu, select Archive. This will build your application and code sign it using the Distribution (Ad Hoc or App Store) profile setup in step 5 of the “Creating the Basic Application” section. Once the build has completed the Organizer window will appear.

http://help.testflightapp.com/customer/portal/articles/494413-how-to-create-an-ipa-xcode-4-3-