When I upload a build to the new Apple owned and iTunes Connect-integrated TestFlight, I see the following log:
WARNING ITMS-90191: "Missing beta entitlement. Your app does not include the beta-reports-active entitlement. If you intend to distribute this build via TestFlight for beta testing, please re-build this app with a newly generated provisioning profile."
When I look at the build on iTunes Connect, I also see the following warning:
To use TestFlight Beta Testing, build X.Y.Z must contain the correct beta entitlement. For more information, see the FAQ.
The linked FAQ states:
What should I do if my prerelease build does not contain the correct beta entitlement?
To use the TestFlight app to test your prerelease build, it must be signed with an App Store Distribution Provisioning profile that includes the beta entitlement. New Distribution Provisioning profiles generated in the iOS Developer Center will automatically contain the beta entitlement.
If you have an existing Distribution Provisioning Profile that was generated before the launch of TestFlight Beta Testing, you must regenerate the profile.
The problem is that I am using a newly created App Store Distribution Provisioning Profile. I created it like so:
When I inspect the source of the downloaded Provisioning Profile, I see:
<key>Entitlements</key>
<dict>
// ...
<key>aps-environment</key>
<string>production</string>
<key>beta-reports-active</key>
<true/>
// ...
So the Provisioning Profile is set for production
and does contain the beta-reports-active
entitlement.
However, iTunes Connect continues to complain when this build is uploaded to TestFlight.
Any ideas on how to fix this issue? Is this an Apple bug?
rdar://20128048
See Question&Answers more detail:
os 与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…