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.

Translate

stolennickname

Inspiring

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"

Translate

R

Roshan Chhetri

Adobe Employee

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.

Translate

R

Roshan Chhetri

Adobe Employee

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

Translate

piyushb89979246

Adobe Employee

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

Translate

R

Roshan Chhetri

Adobe Employee

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

Translate

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.