Skip to main content
H
Harry248
Inspiring
December 11, 2015
Question

"Bundle is invalid" in iTunes Connect using latest AIR SDK 20

  • December 11, 2015
  • 28 replies
  • 19117 views

Compiling with the latest AIR SDK (20.0.0.215) I get a "This build is invalid" error in iTunes Connect. Any idea?

    This topic has been closed for replies.

    28 replies

    Show previous replies
    Reactor13
    Reactor13
    Inspiring
    February 1, 2016

    The same problem on windows...

    Dear Adobe, сritical problems in AIR SDK are too often lately...

    D
    danielg69019501
    Participant
    February 1, 2016

    I am also looking for a solution to this "build is invalid" issue when building on Windows.

    V
    vslav_i_e
    Participating Frequently
    January 29, 2016

    What do we do on Windows?!!!!!!!!!!!!!!!!!!!!!!!!!


    AIR 18 IPA builds, uploaded without ERRORS, but i need AIR 20 because iPad PRO supported...

    C
    ClaytonW
    Participant
    January 22, 2016

    I have the same problem. Is there any workaround for Windows? I really don't want to do this on Mac...

      S
      Saframan
      Participating Frequently
      January 25, 2016

      What do we do on Windows? Like ClaytonW I have the same Problem and don't have a Mac available

        stolennickname
        stolennickname
        Inspiring
        January 6, 2016

        This is still occurring with AIR 20.0.0.233.

        J
        jon_huang
        Participating Frequently
        December 31, 2015

        Thanks for publishing the workaround, I was lurking this thread while worried. Anyway, I was able to follow these instructions and upload a build:


        [iOS ] "This build is invalid" error in iTunesConnect while uploading app

        • This issue has been fixed on Mac. To package the app correctly, so that it gets uploaded to iTunesConnect without any errors, the developer needs to perform following
        • Add certificate in the Keychain Access of the Mac and provide necessary permission to it while adt accesses the certificate.
        • If doing a remote login (ssh) for packaging the app, an extra command is required. Security unlock <home>/Library/Keychains/login.keychain for successful packaging.

        "provide necessary permission" is a bit ambiguous, but basically open the private key and Get Info, then add the app permissions.

        stolennickname
        stolennickname
        Inspiring
        January 6, 2016

        This workaround is listed in the fixed issues section of the release notes, but I can't get it to work. I continue to get an invalid signature on the resultant ipa.

        In Keychain Access, I've set the Access Control to "Allow all applications to access this item" for all private key children of pertinent certificates. The certificates in question pass validation. I then perform another adt packaging. Performing a spctl check on the ipa reports "rejected source=no usable signature"

        R
        Adobe Employee
        Roshan Chhetri
        Adobe Employee
        January 6, 2016

        Hi, stolennickname‌,

        I request you to perform following steps. We will look into the issue.

        1. Kindly remove the certificate (used for iOS app packaging )from your keychain access.

        2. Add it back to keychain (by double clicking it and providing the password )

        3. DO NOT provide the permission  "Allow all applications to access this item". Let it be "confirm Before Allowing Access".

        4. Package your IPA with the certificate added in the keychain above.

        5. You should get a keychain access permission dialog (Please confirm if you get this?? )

        6. If yes, Please clicks "Allow Once"

        7. IPA should get packaged.

        8. Now, unzip the IPA and perform the following check to the .app file inside unzipped Payload folder

            codesign --verify -vvvv payload/<YourAPP>.app

        9. Please let us know what is the output of the above command when run on your IPA. It will be great if you can let this know to us.

        10. Also, Kindly share the IPA to me    chhetri      (at)           adobe             (dot)    com . OR a dropdown link.

        -Roshan

        Adobe AIR.

        R
        Adobe Employee
        Roshan Chhetri
        Adobe Employee
        December 14, 2015

        Hi Harry248‌, @schussler,

        Thanks for reporting this issue. We have reproduced this at our end and team is looking into this.

        We will update you as soon as we have the fix.

        -Roshan

        Adobe AIR

        piyushb89979246
        Adobe Employee
        piyushb89979246
        Adobe Employee
        December 11, 2015

        Hi,

        Can you please share your project app-xml file at bagri@adobe.com and the other environment details like whether you are using Win or Mac AIR SDK.

        There are some limitations for your bundle id field which you can check here:

        Adobe AIR * AIR application descriptor elements

        Is this was working fine with previous AIR builds?

        -Piyush

        R
        Adobe Employee
        Roshan Chhetri
        Adobe Employee
        December 11, 2015

        Hi, Can you follow the instructions mentioned in http://fpdownload.macromedia.com/pub/labs/flashruntimes/shared/air20_flashplayer20_releasenotes.pdf

        [iOS] Bundle errors appearing on uploading app on Appstore (4079233)

        Workaround: User needs to add following tag under InfoAdditions to allow the submission of application in Apple App store.

        <key>UIRequiresFullScreen</key> <true/>

        Also, can you please confirm the Invalid Signature issue appears again if signed with the Distribution certificate as suggested by Apple.

        -Roshan

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