Skip to main content
P
PixelBerntsen
Participant
September 21, 2013
Question

How do I deliver an UPDATE to an app with Air SDK 3.x

  • September 21, 2013
  • 1 reply
  • 756 views

I'm using Flash Pro CC and I'm trying to deliver a 1.1 update to  an app in the app store.

I get a mail from Apple saying:

Invalid or Non-Increasing CFBundleVersion

Invalid or Non-Increasing CFBundleShortVersionString

Now, it doesn't seem to matter what I write in the publish - version dialog box in Flash Pro CC. Flash Pro CC and Air SDK (3.9) will always set the version number in the -app.xml AND the plist.info file to 1.0.

If I edit the archive directly and change to 1.1, I get an error from the Application Loader saying it has an invalid signature.

I'm wondering if anyone has a solution as I'm a bit desperate to deliver my 1.1 update, and 3.9 is the only SDK working properly with iOS 7.

I have also tried Air SDK 3.8 and the CFBundleVersion won't change there either, no matter what I put in the version number dialogue box of Flash.

Thank you!

This topic has been closed for replies.

1 reply

Colin Holgate
Colin Holgate
Inspiring
September 21, 2013

Try opening the xml in a text editor, then while watching the version number that says 1.0, go into the Flash Pro iOS settings, General, and change the verso to 1.1. Close the publishing dialog. Did you see the version number change? If you didn’t, I think it’s the wrong XML file

P
PixelBerntsenAuthor
Participant
September 21, 2013

I've done this and it doesn't change no matter what I do. Even, if I put 2.0 there and publish to an .ipa file, unzip this file and check the xml in the Payload/META-INF/AIR/Application.xml will read 1.0, and the info.plist has CFBundleVersion and shortversion set to 1.0.

There is simply nothing I can do to change that, and I also tried Flash 6.6 with Air SDK 3.8. Same thing is happening there.

Colin Holgate
Colin Holgate
Inspiring
September 21, 2013

If you move or delete the XML file, and go back into settings, is everything reset? If it is reset, try entering the information again, and see if a new XML file is created, with the right version. If it’s not reset, you moved the wrong file.

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