Skip to main content
C
Colin Childs
Inspiring
December 11, 2013
Question

"Compilation failed..." using "-useLegacyAOT no"

  • December 11, 2013
  • 1 reply
  • 1211 views

I downloaded the new beta (4.0.1320) this morning and tried to use the "-useLegacyAOT no" that was broken in the last build. Doing an Ad-Hoc release build worked great and my build time went from 6:18 down to 1:45, which is awesome. Strangely, I get a very unhelpful compilation error when trying to do a Standard packaging method run/debug using the same settings. Any ideas of what may be going wrong? Here is the FlashBuilder error log:

!STACK 0
java.lang.Exception: 
Compilation failed...
at com.adobe.flexide.multiplatform.ios.launching.IOSLaunchHandler.doPackage(IOSLaunchHandler.java:704)
at com.adobe.flexide.multiplatform.ios.launching.IOSLaunchHandler.launch(IOSLaunchHandler.java:255)
at com.adobe.flexide.launching.multiplatform.MultiPlatformLaunchDelegate.launch(MultiPlatformLaunchDelegate.java:184)
at com.adobe.flexide.launching.AbstractFlexLaunchDelegate.launch(AbstractFlexLaunchDelegate.java:244)
at com.adobe.flexide.launching.AbstractFlexLaunchDelegate.launch(AbstractFlexLaunchDelegate.java:134)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:928)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1132)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
This topic has been closed for replies.

1 reply

S
Adobe Employee
sakjain1
Adobe Employee
December 12, 2013

Hello,

Could you please share the sample project along with all the resources in which issue is reproducible so that we can investigate it at our end.Also,please confirm the platform on which you compiling your app - Windows or Mac?

Thanks,

Sakshi Jain

Adobe AIR Team

C
Colin ChildsAuthor
Inspiring
December 12, 2013

Because I cannot supply the current project I am working on, I tried to reproduce the issue with a fresh project. Every time I try to debug the app on an iOS device, it now gives me the error "The command line is too long. Compilation failed while executing : compile-abc". Here are the steps I took to cause this error:

1) In Flash Builder, create a new Flex Mobile project.

2) In the app.xml, change the app ID to match that of your iOS signing keys.

3) In the project properties, add the packaging command "-useLegacyAOT no".

4) Create a new debug configuration. Change the launch method to "On device" using the "Standard" packaging method.

5) Try to debug using the configuration created in step 4.

Additionally, I tried running this command from the command line. I did so by going back to my debug configuration and clicking on "Customize launch..." then copying the result of "Show Command...", altering the parameters as needed (adding quotes around paths, including the storepass parameter). When running it though the command line instead of through FB, I still got the same error. The stack trace shown in the FB logs is the same as that of the previous error.

Also, I am doing all of this on Windows 7.

S
Adobe Employee
sakjain1
Adobe Employee
December 13, 2013

Hi,

This is a known issue with debug swfs on Windows.As a workaround, you may compile your app using release/optimized swf.

Thanks,

Sakshi

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