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

Report · Dec 11, 2015

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

Report · Apr 06, 2016

Hi All,

The issue of invalid build has been fixed on both Win and Mac AIR SDK's.

Please find the fix here: Download Adobe AIR 22 Beta - Adobe Labs

Kindly let us know if you have any queries.

-Roshan

Adobe Air

Report · Apr 16, 2016

Thank you for the fix Roshan, but this AIR 22 Beta crashes my app.

It auto closes at random times. I just gave up trying to update my app..this needs serious work.

Report · Apr 20, 2016

Hi,

Let us know if you are facing the issue with an API?

Also, I request you to kindly log a bug in : bugbase with a sample project.

-Roshan

Adobe AIR.

Report · Apr 22, 2016

Thanks, but is this major issue going to be fixed also in AIR21?

Report · Apr 26, 2016

Our team is working on this. We will let you know about this fix coming in Build 21 soon.

-Roshan

Report · Apr 27, 2016

Unfortunatelly the AIR 22 beta does not fix the problem. Aplication Loader send file, but it still cannot be submit for review. The error message:

"We have discovered one or more issues with your recent delivery for "XXXXXXX". To process your delivery, the following issues must be corrected:

Invalid Bundle - The bundle at '/Payload/XXXXX.app' does not contain a bundle executable.

Once these issues have been corrected, you can then redeliver the corrected binary. ".

So right now we have about 6 moths of total disable of ability to sending our apps to AppStore.

And when I read advices like "Switch to Mac platform" - it is not even funny. Try consider that I already spend lot of money to buy Adobe Production Premium Box (cost is more-less one year of income, here in Poland). Now You try to tell me to spend another one to switch to Mac - thanks for advice.

Another thing - if You tell us, that we should use older wersion of AIR SDK 20.0.0.204- where we can find it?
Why You cannot upload it and give us a right-now-only-solution to send apps to AppStore. Please, don't You understand, that we have also some deadlines, clients who can make Your customers big problems - just because they belive that there is possibility to create iOS Apps with AIR platform?

If you still don't give us really working solution we are consider to make some representative action. Tomorrow I want to talk about it with my lawyer. Esspecially, because on "Download Adobe AIR SDK" page You still telling lies like "for the delivery of out-of-browser applications and games across devices and platforms (Windows, Mac, iOS, Android).". And You know that is not working from December 2015!

I understand, that you have some other issues, but WHAT IS MORE IMPORTAND TASK, over give us ability to send uor apps for AppStore?

Report · Apr 27, 2016

@cyprian_far have you confirmed that Ad Hoc builds work locally? It sounds like this might not be a signing error but maybe some other issue with AIR 22 or your project setup. Try AIR 20 or AIR 19 if you haven't yet. I think the only major limitation with them is lack of support for new devices like the giant ipads. They're here if you can't find them:

Find and download archived versions of Adobe AIR SDK

Report · Apr 27, 2016

Yes, I tested it Ad Hoc, and everything work just fine...

I also check Archive download page, but there is only Adobe AIR 20.0.0.260 version (I also check the 20.0.0.233, 20.0.0.260, 21.0.0.176, 21.0.0.198 and newest 22.0.0.97). It is always the same - works perfect Ad Hoc locally. Cannot add Build in the Itunes Connect....

Before i work on 18.0.0.180 and there was no such a things.

I think that my issue can be 3 ANE's: facebook, store kit and core mobile (for common things as confirmation or alert).

Adobe Team - sorry for my furious previous post, but before I found this page - I spend nights follow Apple's reports about invalid signature in certicate and revoke my certificates ect...
I know that you are dooing all the best you can - for us!

Report · Apr 27, 2016

Hi @cypro faro

What message do you see when you unzip the ipa-app-store ipa and run below codesign command?

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

-Roshan

Adobe AIR

Report · May 21, 2016

Roshan, it's been 4 weeks since you said "Our team is working on this".

You've obviously got a solution because the issue doesn't exist in Air 22 beta.

And you've had one update to AIR 21 in the last 2 weeks.

So WHY AIR 21 (the latest non-beta option) STILL NOT WORKING with App Store submissions?

Every extra person who manages to find this thread reports the same thing- hours and hours wasted on revoking certificates and trying all sorts of thing just to discover finally that it's a KNOWN BUG that Adobe DOESN'T have noted on the download site... that's buried away in this thread.

How many people do you need to go through the same angst; how many people do you need to appear to want to drive AWAY from AIR; before you'll finally roll out a fix or at the very least make it DAMN OBVIOUS that APP STORE SUBMISSION IS MUNTED.

Fix the bug.

Fix the communications.

Stop driving developers away.

Please.

Report · May 21, 2016

Hi @Minty Hunter

We have got the solution for AIR 21 SDK as well. Please go to the following link : Find and download archived versions of Adobe AIR SDK and download the 21.0.0.215 SDK.

We understand that windows signing has been a really big issue to our developers for last few months and same has concerned Adobe AIR team as well.

On 12th may we released a Version 21 SDK that had the fix and listed the issue has been fixed please read here: Flash Player Help | Release Notes | Flash Player® 21 AIR® 21

We missed to update this forum thread about the fix because there were many such threads that queried us. Request you to go through the release posted above and try the Windows fix.

Let us know if it is fixed or even if it is not. Adobe AIR team is more than happy to solve your issues.

-Roshan

Adobe AIR

Report · May 22, 2016

Roshan,

Thanks for the prompt response. I had already downloaded 21.0.0.215 and I'd gone to the release notes and seen this:

"May 12, 2016

In today's scheduled release, we've updated Flash Player and AIR with important bug fixes and security updates."

... but I missed the fact that I needed to scroll down past all the other release notes, past "How to update the Flash player" and "How to contact us" ... to finally reach the bit where it details WHAT the bug fixes were.

If you have a major fix like this, would it not make sense to make it MORE prominent? Why not put the full fixes for the latest version right at the top rather than bury it down the page??

So frustrating- you've actually fixed it and then done a terrible job of TELLING developers. (Or maybe I was just being super-thick by not scrolling right down....)

Report · May 22, 2016

Hi Minty Hunter,

Thanks for your response. We take a not of your feedback and see if this can be done in future.

-Roshan

Report · Apr 21, 2016

I too have spent hours uploading builds (IPA created on Windows box, taken across to Mac and uploaded with XCode), getting the all clear from Application Uploader, only to then get an email that says "- The binary with bundle identifier XXXX contains an invalid signature."

I tried re-issuing my certificate and changing profiles and changing the TYPE of publishing in Flash (Device Testing/Apple App Store/Ad Hoc etc)... and each time hit the same problem.

I finally found this thread and downloaded AIR 22 Beta on my Windows box... and without changing anything else, I now get an email that says

"The following build has completed processing"

I'm probably lucky in that I'm not using any of the ANEs that others are reporting broken in v22.

But how in hell do you have such a critical (and misleading and frustrating) KNOWN ISSUE, and NOT post it on the SDK download page?

SUGGESTION: If you have a known critical bug across multiple AIR releases, HIGHLIGHT IT ON THE DOWNLOAD PAGE and save massive frustration.

Report · Apr 24, 2016

Confirmed that the AIR 22 beta does sign app store IPAs correctly on Windows.

I wish I'd found this thread before wasting a day uploading bad builds and having to increment my build number each time... thanks Apple. Well they do deserve at least half the blame for causing a new signing fiasco with every version of iOS - I've never had this trouble with Android.

Report · May 20, 2016

Wow... so this is what is going on... so many rent hours wasted in macincloud trying to upload via application loader 3.0...