Skip to main content
blogtom
Known Participant
Dec 6, 2014 3:53 PM UTC
Question

Air iOS - To use TestFlight Beta Testing, build 1.0.0 must contain the correct beta entitlement.

Hi,

I published my iOS app and uploaded it to iTunes Connect to run an external beta test through Apple TestFlight but I got this error:

To use TestFlight Beta Testing, build 1.0.0 must contain the correct beta entitlement.

I created my certificate 3 days ago and it contains the beta entitlement.

I published the iOS app with the latest Flash CC 2014 version on a Mac with Air 15.

How to fix that error?

Thanks

This topic is closed to new replies. Start a new post to keep the conversation going.

17 replies

StephenPS
Inspiring
Jul 6, 2015 2:57 PM UTC

This worked well for me as well.

One thing further to note though, if you go back to doing local builds direct to device you may get a verification error if the Beta Entitlement is still in there, which it can be.  My solution now is to maintain two versions of the text file yourappname-app.xml swapping the one not currently being used to another holding name.  Make both files read only and make sure the one for the iTunesConnect includes the Beta Entitlement line whilst the other does not.  Of course if you make other changes (such as the version number) you'll have to go back into the file, temporarily make it writable, make the change you want then make it read only again.

This is a bit of a hassle and really Adobe should fix this.  I was surprised it was not catered for within the latest version of Flash Professional CC 2015 - where an Ad Hoc build is selected the Beta Entitlement should not be included, whereas where an App Store build is requested it should be.

Translate
    blogtomAuthor
    Known Participant
    Jun 10, 2015 3:21 PM UTC

    I'm using the beta entitlements also in the XML for the final store submission - that way I'm able to easily test the uploaded final build on the device! (to make sure the .ipa file got uploaded correctly)

    Translate
    Colin Holgate
    Colin Holgate
    Inspiring
    Jun 10, 2015 3:26 PM UTC

    Surely the app gets rejected if it has the beta entitlements still in it? Also, to test on devices you would be using an Ad Hoc provisioning profile, and you need an App Store one for the final submission.

    Translate
    blogtomAuthor
    Known Participant
    Jun 10, 2015 3:36 PM UTC

    My app didn't get rejected - even WITH the beta entitlements in it.

    Translate
    Projectitis
    Projectitis
    Inspiring
    Jun 2, 2015 2:45 AM UTC

    Can anyone confirm - if building for local testing (e.g. connect with cable) and not the app store build, that adding the <Entitlements> will result in an installation error?

    Installing application for testing on iOS (192.168.1.9)

    Installation Error: ApplicationVerificationFailed.

    Translate
    Colin Holgate
    Colin Holgate
    Inspiring
    Jun 2, 2015 2:53 AM UTC

    I don't think the beta entitlements would stop local testing from working, but you could just remove those to make sure. Also, make sure you're using distribution Ad Hoc for local testing, and beta entitlements App Store for TestFlight.

    Translate
    Projectitis
    Projectitis
    Inspiring
    Jun 2, 2015 3:33 AM UTC

    I haven' built the app with Entitlements for the store yet, but adding the Entitlements breaks local testing (ipa-test and ipa-test-interpreter).  No problem commenting them for local testing, but just checking whether there are deeper reasons.

    Translate
    CR Photo
    Participating Frequently
    Jan 22, 2015 2:41 AM UTC

    Any chance you figured this out?  I'm having the same problem.

    Translate
      CR Photo
      Participating Frequently
      Jan 22, 2015 3:37 PM UTC

      I was able to get TestFlight working based on a comment in the following bug report:

      Bug#3845110 - Wrong beta entitlement for TestFlight Beta Testing in iTunesConnect

      In summary... I am using Air SDK 16.0 and added the following to my app xml file:

      <Entitlements>

      <![CDATA[ <key>get-task-allow</key>

      <false/>

      <key>beta-reports-active</key>

      <true/> ]]>

      </Entitlements>

      I uploaded a new build to Apple using Application Loader 3.0 and I was then able to submit my app for beta review.

      Translate
        Colin Holgate
        Colin Holgate
        Inspiring
        Jan 22, 2015 4:35 PM UTC

        To get test flight to work, was the IPA built as Ad Hoc or App Store?

        Translate
        SHEPHERDclif
        Inspiring
        Jan 6, 2015 6:33 PM UTC

        Did you ever figure this out? I'm setting it up for the first time and one I'm not exactly sure how I add the beta enttilement to the Dist provision as most of the documentation I come across discusses xcode. I've done the step of setting up in itunes connect but as for the provision do I just do a new download of the mobileprovision or do I actually have to select something along with the other devices I've already selected for the provision?

        Translate
        SHEPHERDclif
        Inspiring
        Jan 6, 2015 6:33 PM UTC

        Oh, and just noticed this is under Air iOS I'm actually trying to use TestFlight for a DPS app.

        Translate
        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices