Using TestFlight with CloudKit development environment

Question

Is it possible to submit an app to the new TestFlight via iTunes Connect using the "Development" environment for CloudKit?

It seems that only AdHoc Provisioning Profiles ask for the preferred CloudKit container name (Production or Development) when doing an "Export" from Organizer, however AdHoc Provisioning profiles do not contain the "beta-reports-active" entitlement required to submit apps to iTunes Connect and allow TestFlight use.

SO it would seem if you want to use the new iTunes Connect version of TestFlight to test your CloudKit-based app, you have to use the Production environment. Has anyone else had this issue?

Answer 1

I have also tried to do that, but I don't think it is possible. TestFlight is primarily for apps "that you intend for public release on the App Store." If you are beta testing with iTunes users, Apple expects you to be using the Production server, as the users will expect their content to survive over to the released product.

Personally, I just decided to switch to Production when I started using TestFlight. If you are just testing with internal users, then you still have the option of Ad Hoc distribution, which as you point out allows you to use either server.

By the way, you can change the server locally, so you can test Production from your debug builds.

The documentation states:

At runtime, CloudKit uses your app’s com.apple.developer.icloud-container-environment entitlement to discover whether you are using a Development or Production version of your provisioning profile.

So you can add this to your entitlements to set it to Production or Development:

<key>com.apple.developer.icloud-container-environment</key> <string>Production</string> 

You could try setting this field to Development and then pushing to iTunes Connect, but I'm guessing that Xcode will overwrite it during the upload to force you to use Production.