Highlighted

A fatal ADT package error, possibly caused by Flex 4.12 with AIR 13 SDK!!

Participant ,
Apr 25, 2014

Copy link to clipboard

Copied

Hi,

I've just downloaded Flex 4.12 & AIR 13 & Flash Player 13 with Flex SDK Installer 2.7 today, they are all production release versions, I correctly import the 4.12.0 SDK folder to my Flash Builder 4.7 (x64 on Windows 7 x64) like I always do.

Then I try to export release for my Flex Mobile Project to the AdHoc IPA file, the bin-release-temp folder and all of its contents (MyDemo.swf, MyDemo-app.xml, and subfolders etc.) are successfully generated, but when I click Finish Button inside the Export Release Build Window, ADT starts to package the bin-release-temp contents, just after a few seconds, Flash Builder popups an error window says:

"Error occurred while packaging the application:"

"D:\VLP\FLEX\MyDemo\bin-release-temp\AOT\MyDemo-app.xml: error 308: File  is missing from the package"

(I carefully watched the files inside the AOT folder, the MyDemo-app.xml file was there each time it started to package, so it's not missing at all! But when Flash Builder popups the error above, the AOT folder is automaticly deleted from the bin-release-temp folder)

Then I try to add "-useLegacyAOT no" before "-provisioning-profile" to Customize Launch, which results in the same error above!

When I used Flex 4.11 (or earlier versions) + AIR 4 (or earlier versions) + Flash Player 12 (or earlier versions), I can package the same flex mobile project (MyDemo) to AdHoc IPA with no errors at all, one thing to notice is that I did not use "-useLegacyAOT no" to Customize Launch at that time.

I don't know whether it's an AIR 13.0.0.83 SDK bug or Flex 4.12.0 SDK bug, but it's a fatal one for Flex Mobile Projects! (BTW there is no problem with pure ActionScript Mobile Projects)

Could anyone please have a look at this issue, thanks to any further replies!

DarkStone

2014-04-25

Hi Chris,

I have confirmed this is an AIR SDK 13.0.0.83 bug.

I have reported this bug to Adobe Bugbase, and I also included the workaround:

https://bugbase.adobe.com/index.cfm?event=bug&id=3750892

The workaround is:

Simply comment the <externalSwfs> tag in your -app.xml will solve this bug, like this: <!-- <externalSwfs></externalSwfs> -->

DarkStone

2014-04-28

TOPICS
Performance issues

Views

1.1K

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

A fatal ADT package error, possibly caused by Flex 4.12 with AIR 13 SDK!!

Participant ,
Apr 25, 2014

Copy link to clipboard

Copied

Hi,

I've just downloaded Flex 4.12 & AIR 13 & Flash Player 13 with Flex SDK Installer 2.7 today, they are all production release versions, I correctly import the 4.12.0 SDK folder to my Flash Builder 4.7 (x64 on Windows 7 x64) like I always do.

Then I try to export release for my Flex Mobile Project to the AdHoc IPA file, the bin-release-temp folder and all of its contents (MyDemo.swf, MyDemo-app.xml, and subfolders etc.) are successfully generated, but when I click Finish Button inside the Export Release Build Window, ADT starts to package the bin-release-temp contents, just after a few seconds, Flash Builder popups an error window says:

"Error occurred while packaging the application:"

"D:\VLP\FLEX\MyDemo\bin-release-temp\AOT\MyDemo-app.xml: error 308: File  is missing from the package"

(I carefully watched the files inside the AOT folder, the MyDemo-app.xml file was there each time it started to package, so it's not missing at all! But when Flash Builder popups the error above, the AOT folder is automaticly deleted from the bin-release-temp folder)

Then I try to add "-useLegacyAOT no" before "-provisioning-profile" to Customize Launch, which results in the same error above!

When I used Flex 4.11 (or earlier versions) + AIR 4 (or earlier versions) + Flash Player 12 (or earlier versions), I can package the same flex mobile project (MyDemo) to AdHoc IPA with no errors at all, one thing to notice is that I did not use "-useLegacyAOT no" to Customize Launch at that time.

I don't know whether it's an AIR 13.0.0.83 SDK bug or Flex 4.12.0 SDK bug, but it's a fatal one for Flex Mobile Projects! (BTW there is no problem with pure ActionScript Mobile Projects)

Could anyone please have a look at this issue, thanks to any further replies!

DarkStone

2014-04-25

Hi Chris,

I have confirmed this is an AIR SDK 13.0.0.83 bug.

I have reported this bug to Adobe Bugbase, and I also included the workaround:

https://bugbase.adobe.com/index.cfm?event=bug&id=3750892

The workaround is:

Simply comment the <externalSwfs> tag in your -app.xml will solve this bug, like this: <!-- <externalSwfs></externalSwfs> -->

DarkStone

2014-04-28

TOPICS
Performance issues

Views

1.1K

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Apr 25, 2014 0
Participant ,
Apr 25, 2014

Copy link to clipboard

Copied

I have posted this issue to Apache Flex forum: http://apache-flex-development.2333347.n4.nabble.com/A-fatal-ADT-package-error-possibly-caused-by-Fl...

Just in case it's a Flex 4.12.0 SDK bug.

DarkStone

2014-04-25

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 25, 2014 0
Adobe Employee ,
Apr 25, 2014

Copy link to clipboard

Copied

Could you please open a new bug report on this over at https://bugbase.adobe.com?  When adding the bug, please include some sample code or a sample application so we can quickly test this out internally.  If you'd like to keep this private, feel free to email the attachment to me directly (ccampbel@adobe.com). 

Once added, please post back with the URL so that others effected can add their comments and votes.

Thanks,

Chris

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 25, 2014 0
Participant ,
Apr 28, 2014

Copy link to clipboard

Copied

Hi Chris,

I have confirmed this is an AIR SDK 13.0.0.83 bug.

I have reported this bug to Adobe Bugbase, and I also included the workaround:

https://bugbase.adobe.com/index.cfm?event=bug&id=3750892

The workaround is:

Simply comment the <externalSwfs> tag in your -app.xml will solve this bug, like this: <!-- <externalSwfs></externalSwfs> -->

DarkStone

2014-04-28

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 28, 2014 0
Adobe Employee ,
Apr 28, 2014

Copy link to clipboard

Copied

Thank you!  I'll have the team follow up asap.

Chris

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 28, 2014 0