IOS Export Release Build hangs with FB4.7

I recently updated to FB4.7 running AIR 3.4 on my Macbook Air under Lion 10.7.5.
My project contains a large number of embeded files and when debugging under FB4.6 I was often encountering Java Heap Errors and lots of out of memory errors. However, I was able to put up with those errors and still export working release builds.
Under FB4.7 I am able to compile DEBUG builds now without the problems I was having under FB4.6. However, when I attempt to export an iOS release build using the IDE under FB4.7 the process always just hangs (at Packaging 0%) and never completes (even after waiting hours).
If I create a small test project under FB4.7, I am able to export a release build successfully. So I believe my FB install is working.
I've tried bumping up the xms and xmx settings in the Flash Builder 4.7.ini file to 2048m, but that has made no difference to the problem.
I suspect that the large number of embeded files that I have in my project may be contributing to the problem. The embeded files are primarily all UI artwork as my app supports all the different iOS screen resolutions.
Short of restructuring my entire project to remove all the embeded files (which I really do not want to do at this point) is there anything else that can be done to get FB4.7 to succesfully export an iOS release build?

Hi Sanjay,
Thanks for the quick reply! Hereby the extra info:
1. -Xmx2048m
2. We are using ATF files with all three textures included (around 14 MB for @2x and 8 MB for @1x). We could exclude the DXT and ETC ones, but than we need to create them for all separately. Thereby we are not done with the project so the size will still increase, than it is a solution for a short time.
3. I just tried with the following results:
At the beginning it is giving some warnings:
Exception in thread "main" com.adobe.air.ipa.ProcessError: Assembler failed
          at com.adobe.air.ipa.AOTCompiler.launchProcess(AOTCompiler.java:271)
          at com.adobe.air.ipa.AOTCompiler.compileModule(AOTCompiler.java:1444)
          at com.adobe.air.ipa.AOTCompiler.compileBitcodeImpl(AOTCompiler.java:1342)
          at com.adobe.air.ipa.ASMGenerator.main(ASMGenerator.java:68)
Exception in thread "main" com.adobe.air.ipa.ProcessError: Assembler failed
          at com.adobe.air.ipa.AOTCompiler.launchProcess(AOTCompiler.java:271)
          at com.adobe.air.ipa.AOTCompiler.compileModule(AOTCompiler.java:1444)
          at com.adobe.air.ipa.AOTCompiler.compileBitcodeImpl(AOTCompiler.java:1342)
          at com.adobe.air.ipa.ASMGenerator.main(ASMGenerator.java:68)
Undefined symbols for architecture armv7:
After that, a lot of lines are shown with this at the end:
ld: symbol(s) not found for architecture armv7
Compilation failed while executing : ld64
Any idea?
Thanks,
Ben

Similar Messages

  • Export release build failed with an error message: complilation failed while excuting : compile-abc

    I updated air sdk from 4.0 to 16.0 beta to fix apple app store submitting bug. I can build the project and run it on simulator without any problem.  But when I tried to export the ios release build, I got this error message: complilation failed while excuting : compile-abc. 
    I use commmand line to excute compile-abc.exe with the parameters that adt gives it, but it failed without any error message.
    Here is the command line:
    compile-abc.exe -mtriple=armv7-apple-ios -filetype=obj -sdk "C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.5\sdks\4.5.1 - air16\lib\aot/lib/avmglue.abc" -fields "C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.5\sdks\4.5.1 - air16\lib\aot/lib/air-fields.arm-air.txt" -O3 -abc-file-list=E:\MyApp\bin-debug\AOTBuildOutput8184169967790207636.tmp\ABCFilesList.txt
    There's a empty file AOTBuildOutput-0000001821_1821.o left in the command line workaroud path. I opened file AOTBuildOutput-0000001821.abc, but didn't get any clue. How can I trace this problem?

    Still having similar issues - seems to be when I embed an image - but works for every release except for release build
    Tried your work around but doesnt seem to make a different
    [Embed(source = "/../assets/[email protected]")]
    protected static const ATLAS_IMAGE:Class;
    [Embed(source = "/../assets/[email protected]", mimeType = "application/octet-stream")]
    protected static const ATLAS_XML:Class;
    [Embed(source = "/../assets/iconMap.png")]
    protected static const ATLAS_IMAGE_LOW_RES:Class;
    [Embed(source = "/../assets/iconMap.xml", mimeType = "application/octet-stream")]
    protected static const ATLAS_XML_LOW_RES:Class;
    if(Starling.current.viewPort.width > 320)
    atlas = new TextureAtlas(Texture.fromBitmap(new ATLAS_IMAGE(), false), XML(new ATLAS_XML()));   
    }else{
    atlas = new TextureAtlas(Texture.fromBitmap(new ATLAS_IMAGE_LOW_RES(), false), XML(new ATLAS_XML_LOW_RES()));

  • Export Release Build - Problem with Server Settings

    Hello, i have a big problem and i searched the whole day yesterday but didnt found an answer...
    I started a Flex Mobile and PHP Project. The Project has a Data/Services included wich loads some customer from a database (sql)... for the first a
    used Zend and try it local (http://localhost and used the htdocs Folder of Zend)... EVERYTHING WORKS PRETTY FINE... so NOW my problem
    I wanted to export this project to a release build for my android phone... so the first warning of Flash Builder ist that the project ist currently configured to access data services from a local url. Before exporting the application, you may need to deploy your services to a remote server, then change the server root URL for your project. Click here to change server settings.
    When i click the button i get the server setting.
    Web root: C:\Program Files (x86)\Zend\Apache2\htdocs
    Root URL: http://localhost
    whe i change it now i get an eror:"The selected web root folder does not exist (i attached i screenshot of it).
    i entered de domain of my server (i also tried the ip) at Root URL. And i think there ist a problem with the Web root...? i get scary

    i know WHY Flashbuilder tells me that i have to change the setting when i deploy on the device
    my problem ist that i got this error...
    and the domain wich i have in the screenshot should only explain how i tried it...
    i entered my server url (the real domain) and i entered the folder "app" wich i have created via ftp on my server...
    BUT i also get this error (lik in the screenshot)
    i think at ROOT URL i cant make lot mistakes .... http://myserver.de or the ip
    but i think maybe my web root ist incorrect? i entered here the folder wich is directliy on my server...?
    i dont know exactly but i got an error like in the screen

  • Export release build fails with project created by Launchpad

    When I try to export a release build (using Flash Builder 4.5) of a project created in Adobe Air Launchpad (p8_3-0-1_081911) I get the following error message:
    "error occurred while saving the project settings: 'default' build target cannot be found for the selected project"
    Is this a bug or am I doing something wrong? Any help/ideas would be greatly appreciated!
    Rob

    I solved this by creating a new project and copying everything across. But it was time-consuming work - especially creating all the new value objects and data services. Air Launchpad is a great concept and has helped me a lot, but this particular forum is dead.
    Rob

  • Flash Builder export release build fails with lot of assets

    I'm having troubles when building for release and when running with "standard" packaging. It just hangs without having a error notification or so.
    The project I'm packaging has a lot of assets, like 150 MB. When trying to package with the "fast" packaging option, it is working realy good!
    I tried to increase the vm arguments in the .ini settings file, but without succes.
    Do you have any suggestion?

    Hi Sanjay,
    Thanks for the quick reply! Hereby the extra info:
    1. -Xmx2048m
    2. We are using ATF files with all three textures included (around 14 MB for @2x and 8 MB for @1x). We could exclude the DXT and ETC ones, but than we need to create them for all separately. Thereby we are not done with the project so the size will still increase, than it is a solution for a short time.
    3. I just tried with the following results:
    At the beginning it is giving some warnings:
    Exception in thread "main" com.adobe.air.ipa.ProcessError: Assembler failed
              at com.adobe.air.ipa.AOTCompiler.launchProcess(AOTCompiler.java:271)
              at com.adobe.air.ipa.AOTCompiler.compileModule(AOTCompiler.java:1444)
              at com.adobe.air.ipa.AOTCompiler.compileBitcodeImpl(AOTCompiler.java:1342)
              at com.adobe.air.ipa.ASMGenerator.main(ASMGenerator.java:68)
    Exception in thread "main" com.adobe.air.ipa.ProcessError: Assembler failed
              at com.adobe.air.ipa.AOTCompiler.launchProcess(AOTCompiler.java:271)
              at com.adobe.air.ipa.AOTCompiler.compileModule(AOTCompiler.java:1444)
              at com.adobe.air.ipa.AOTCompiler.compileBitcodeImpl(AOTCompiler.java:1342)
              at com.adobe.air.ipa.ASMGenerator.main(ASMGenerator.java:68)
    Undefined symbols for architecture armv7:
    After that, a lot of lines are shown with this at the end:
    ld: symbol(s) not found for architecture armv7
    Compilation failed while executing : ld64
    Any idea?
    Thanks,
    Ben

  • FB4 Export Release Build fails

    I am having problems exporting a release build of my application.   Nothing appears to happen when I Project => Export Release Build.
    Any help would be appreciated.
    Below is the stack trace taken from the workspace's .log file:
    !ENTRY org.eclipse.ui 4 0 2010-04-10 12:09:57.919
    !MESSAGE Unhandled event loop exception
    !STACK 0
    java.lang.NoClassDefFoundError: com/adobe/flexbuilder/exportimport/releaseversion/ui/ExportContentPage$ExportFileChooser$ ExportViewerFilter
        at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportContentPage.createControl(Expo rtContentPage.java:106)
        at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:170)
        at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportReleaseVersionWizard.createPag eControls(ExportReleaseVersionWizard.java:310)
        at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:675)
        at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:549)
        at org.eclipse.jface.window.Window.create(Window.java:431)
        at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089)
        at com.adobe.flexbuilder.exportimport.releaseversion.ExportReleaseVersionAction$1.run(Export ReleaseVersionAction.java:93)
        at com.adobe.flexbuilder.exportimport.releaseversion.ExportReleaseVersionAction.run(ExportRe leaseVersionAction.java:103)
        at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
        at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:229)
        at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionI tem.java:584)
        at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
        at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java :411)
        at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
        at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
        at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3910)
        at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3503)
        at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
        at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
        at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
        at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
        at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
        at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
        at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
        at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
        at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLau ncher.java:110)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.jav a:79)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
        at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
        at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
    Caused by: java.lang.ClassNotFoundException: com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportContentPage$ExportFileChooser$ ExportViewerFilter
        at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:494)
        at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410)
        at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:398)
        at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.jav a:105)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
        at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
        ... 38 more

    I did a little more testing...
    I am using MyEclipse 8.5 as my IDE.  I placed the Flash Builder plugin folder in my MyExclipse profile's 'dropins' folder and restarted MyEclipse.  Everything appears to work as expected except for Project => Export Release Build - as described in my ealier post.
    I have since downloaded and installed the Standalone version of Flash Builder 4.   Using the same workspace and proejcts used in the earlier tests I am able export a release build without a problem.
    Is anyone else have a similiar problem with exporting a release build using Eclipse with the FB4 plugin as I am with MyEclipse?
    Can anyone shead some light as to why I am getting the loop exception using MyEclipse 8.5?
    pwp

  • FB4 - Can't change location for Export Release Build

    FB4 on OSX
    I changed the default location for the "Export Release Build", then I decided to change it back and still uses the previous location no matter what. Restated app, restarted computer, same results. ???

    Did you duplicate the preset and then try to change the copy? Or are you trying to change the original?
    -DH

  • Problem with Export Release Build

    My App works fine in the emulator and with the Apple development certificates when installed on my iPad.
    Today I created the correct distribution credentials (certificates, etc.) to get it ready for the App store.
    I go through the "export release build" process and FB does its thing.
    What happens next is that the green status bar never goes past 0%.
    It just sits there for about 5 minutes then the "export release build" dialog window goes away.
    I get no errors or alerts of any kind.
    It does create an .IPA file, but when I try to load it on my iPad I get a "failed to install" error.
    Any suggestions on what I can do?
    thanks

    i know WHY Flashbuilder tells me that i have to change the setting when i deploy on the device
    my problem ist that i got this error...
    and the domain wich i have in the screenshot should only explain how i tried it...
    i entered my server url (the real domain) and i entered the folder "app" wich i have created via ftp on my server...
    BUT i also get this error (lik in the screenshot)
    i think at ROOT URL i cant make lot mistakes .... http://myserver.de or the ip
    but i think maybe my web root ist incorrect? i entered here the folder wich is directliy on my server...?
    i dont know exactly but i got an error like in the screen

  • Export release build with latest nightly build

    I picked up a night build this week and I noticed when I export release build now I get a bunch of framework sdks and swc files. I need to build something I can email to my supervisors for them to play with the gui I am building. If I try to run the swf it says it does not have permission to access the required framework swf. Is there some way to give it permission to do this? When I did a nightly build with beta2, it created an all encompased swf that I could mail people.
    Thanks for the input.

    Hi,
    You need to go into your project settings a set the flex build path to merge code.
    David

  • Error while exporting release build.

    I'm getting this error while exporting release build targeting iOS, running Flash Builder 4.7 and Apache Flex 4.10.0, any help would be greatly appreciated.
    Error occurred while packaging the application:
    # A fatal error has been detected by the Java Runtime Environment:
    #  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000180386950, pid=3328, tid=2472
    # JRE version: 6.0_31-b05
    # Java VM: Java HotSpot(TM) 64-Bit Server VM (20.6-b01 mixed mode windows-amd64 compressed oops)
    # Problematic frame:
    # C  [llvm.dll+0x386950]
    # An error report file with more information is saved as:
    # C:\wamp\www\Flex\ROMCorp\bin-release-temp\AOT\hs_err_pid3328.log
    # If you would like to submit a bug report, please visit:
    #   http://java.sun.com/webapps/bugreport/crash.jsp
    # The crash happened outside the Java Virtual Machine in native code.
    # See problematic frame for where to report the bug.
    Compilation failed while executing : ADT

    My application contains too much private data, I can't attach it. Just several notes about my problem:
    1. It's not reproducible in the Flash Builder 4.6 on OSX 10.6.8
    2. It's reproducible with ant build script
    3. Error is gone when I removed all <icon></icon> elements from descriptor file.

  • Export Release Build error - Exception in thread "main" java.lang.Error: Unable to find named traits

    I've been developing an AIR application for Android and iOS. During development, I've run the application (in debug mode) in the desktop simulator as well as on an iPhone 4 and a Nook Tablet.
    However, I recently tried to "Export Release Build" for iOS and hit the following error: (I've stripped out the package and class information in the error message below)
    !ENTRY com.adobe.flexbuilder.project 4 43 2012-04-06 13:09:15.516
    !MESSAGE Error occurred while packaging the application:
    Exception in thread "main" java.lang.Error: Unable to find named traits: valid.package.path.here::ValidClassName
              at adobe.abc.Domain.resolveTypeName(Domain.java:231)
              at adobe.abc.Domain.resolveTypeName(Domain.java:148)
              at adobe.abc.GlobalOptimizer.sccp_eval(GlobalOptimizer.java:6665)
              at adobe.abc.GlobalOptimizer.sccp_analyze(GlobalOptimizer.java:5909)
              at adobe.abc.GlobalOptimizer.sccp(GlobalOptimizer.java:4628)
              at adobe.abc.GlobalOptimizer.optimize(GlobalOptimizer.java:3514)
              at adobe.abc.GlobalOptimizer.optimize(GlobalOptimizer.java:2215)
              at adobe.abc.LLVMEmitter.optimizeABCs(LLVMEmitter.java:526)
              at adobe.abc.LLVMEmitter.generateBitcode(LLVMEmitter.java:336)
              at com.adobe.air.ipa.AOTCompiler.convertAbcToLlvmBitcodeImpl(AOTCompiler.java:472)
              at com.adobe.air.ipa.BitcodeGenerator.main(BitcodeGenerator.java:82)
    Compilation failed while executing : ADT
    !STACK 0
    java.lang.Exception
              at com.adobe.flexbuilder.project.internal.FlexProjectCore.createErrorStatus(FlexProjectCore. java:1019)
              at com.adobe.flexbuilder.util.logging.GlobalLogImpl.log(GlobalLogImpl.java:66)
              at com.adobe.flexbuilder.util.logging.GlobalLog.log(GlobalLog.java:52)
              at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportReleaseVersionWizard.doPackage (ExportReleaseVersionWizard.java:283)
              at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportReleaseVersionWizard.performFi nish(ExportReleaseVersionWizard.java:152)
              at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827)
              at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432)
              at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
              at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240)
              at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
              at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128)
              at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457)
              at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480)
              at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465)
              at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270)
              at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974)
              at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613)
              at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
              at org.eclipse.jface.window.Window.open(Window.java:801)
              at com.adobe.flexbuilder.exportimport.releaseversion.ExportReleaseVersionAction$1.run(Export ReleaseVersionAction.java:97)
              at com.adobe.flexbuilder.exportimport.releaseversion.ExportReleaseVersionAction.run(ExportRe leaseVersionAction.java:103)
              at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
              at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:229)
              at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionI tem.java:584)
              at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
              at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java :411)
              at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
              at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128)
              at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457)
              at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480)
              at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465)
              at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270)
              at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974)
              at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613)
              at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
              at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
              at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
              at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
              at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
              at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
              at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
              at com.adobe.flexbuilder.standalone.FlashBuilderApplication.start(FlashBuilderApplication.ja va:108)
              at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
              at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLau ncher.java:110)
              at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.jav a:79)
              at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
              at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
              at java.lang.reflect.Method.invoke(Method.java:597)
              at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
              at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
              at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
    The class the error message is referring to is defined with a SWC that my project links to. However, I've even tried to define a class with that same name (and location) within my project and it still fails to find it.
    Why am I able to Project->Clean and run this project within the desktop AIR player (or on the device in debug mode) but unable to export it as a release build?
    I have found a couple of threads mentioning a similar error but none of them have been marked as resolved.

    At this point I feel I am talking to myself, but I will share my work-around in case it helps another who may stumble across this post.
    In my particular case, both my main AIR application and my ANE wrapper library were referencing the same external Flex library (same revision). Both projects had the library linkage set to merge. Changing the linkage to "External" on one of the 2 libraries (it doesn't seem to matter which) and leaving the other as "Merged into code" enabled the export to complete without the bizarre "Unable to find named traits" error.

  • Export release build not including XML data files in apk package

    Hi, all;
    I have a flash pro project that I have packaged for AIR based on these steps:
    http://renaun.com/blog/2011/09/using-flash-builders-mobile-workflow-with-flash-professiona l-projects/
    There are two differences:
    I am loading XML files from right next to the swf
    The Flash Pro project and the Mobile project are sharing a directory that is outside of both projects (this was the workflow already established in FP, since multiple swfs share the same XML).
    When I test this on my phone, it adds the XML files to the apk and everything works great. The problem I am having is that the Export Release Build does not have the XML files included, and I don't see anything in the Flash Builder interface that looks like it will allow me to add other files than the swf and the app.xml.
    What am I missing?

    Thank you so much--your feedback enabled me to think through this and get to the critical piece I was missing. I've marked it helpful, because it pointed the way.
    I'm not a big fan of marking one's own answers "correct," but I'm going to do that this time so that people can easily find the steps.
    The mistake I was making was thinking that the "Debug on device" was not going to push out a debug AIR version, because the swf was not a debug swf.
    I didn't understand that if I clicked the Run button, that this would also push a version out to the device, and that this version would not give the "waiting to connect to the debugger" message.
    The whole process you get when you click "Run" is a little odd (I say this for those who have never tried it). It will install the app to the device, but doesn't launch it (I think it can't). Flash Builder then hangs in "Installing application to device." If you actually look at the screen, you will see a new download in your notifications bar, and from there you can launch the app.
    To summarize:
    To get started packaging your Flash Pro swf for Air using Flash Builder, follow Renaun's steps (http://renaun.com/blog/2011/09/using-flash-builders-mobile-workflow-with-flash-professiona l-projects/)
    In the process of getting this working on Mobile, you probably have a debug version installed on your phone. Uninstall this using Astro File Manager (https://play.google.com/store/apps/details?id=com.metago.astro&hl=en)
    Instead of clicking the "Debug" button in Flash Builder, click "Run." This makes a non-debug apk and pushes it to your phone (if your configuration allows for debugging on the device).
    Additional notes: if you have xml files that are packaged into the apk file and you're using URLLoader (because the app originates as a web app), add "app:/" to the beginning of the URL string you are using. So "xml/myFile.xml" becomes "app:/xml/myFile.xml". If you need to keep your original web app logic, add a conditional on Capabilities.playerType=="Desktop."
    Hope this helps someone else with the same problems

  • Lose access to services on Export Release Build

    I have a web project which uses GraniteDS to interface with java services and works perfectly using Run in FB4.
    However when I use Export Release Build to create the SWF file (and put it into the correct place in my web application), the application can no longer connect to my services. They just silently fail. Why would that be?
    In the project properties, i have Flex Server > Application server type set to BlazeDS with the correct parameters set. My compiler arguments are:
    -locale en_US -services ${STS_WORKSPACE}/library/web-app/WEB-INF/flex/services-config.xml -include-libraries libs/granite-essentials.swc
    Obviously Adobe doesn't support GraniteDS but it seems to me to be an FB4 issue - the connections work fine in development using Run. It's almost as if Export Release Build causes FB4 to ignore the compiler arguments?
    Thanks for any help.

    The SWC is already added there automatically by virtue of being in the libs folder. The compiler option is necessary in addition because the classes in the SWC file are not directly referenced and this option does the following:
    "Links all classes inside a SWC file to the resulting application SWF file, regardless of whether or not they are used.
    Contrast this option with the library-path option that includes only those classes that are referenced at compile time.
    To link one or more classes whether or not they are used and not an entire SWC file, use the includes option.
    This option is commonly used to specify resource bundles."
    Anyway in the meantime I solved the problem. Sorry I said that services were silently failing but this was incorrect, there were error messages in some tests I just did. The cause was that I'm using a framework that does injection based on annotations and when you "export release build" apparently the compiler removes annotations, which it doesn't do in normal development mode, so the objects were not getting injected hence no access to services. I'd actually be interested to know which compiler flag you are using that does this, by the way. In my case I added the following to the compiler arguments and everything started working:
    -keep-as3-metadata+=Bindable,Managed,ChangeEvent,NonCommittingChangeEvent,Transient,Id,Ver sion,Name,In,Inject,Out,Observer,ManagedEvent,Destroy

  • Link ant step to 'Export Release Build'

    We're now managing our assets totally manually, mainly with ant steps, away from Flash Builder's hands, which imo gives us plenty of benefits, but one definite drawback, exporting a release build.  With nearly every other thing you do in Flash Builder, you're able to hook an Ant step to it, but I can't seem to find any place for release builds.
    Currently what we have to do is create the 'bin-release'/'bin-release-temp' (depending on the type of project web/mobile & desktop) and copy our assets in to that folder to be packaged up when we then do a release build.
    Is there any way to automate this step?  All previous attempts to figure out how to have proven to be in vain.
    I don't accept marking an assets folder that contains text and binary files as a source folder and choosing "Copy non-embedded files to the output folder" as a proper solution, as that creates an overhead on Flash Builder that's totally unnecessary and can produce lag while working with it, if you've a large assets folder.
    Thanks for any help ye might be able to give on this, seaders.

    So, even after setting up a new project, the problem didn't go away. Seems as if the problem sits within the libraries I'm using, though none of them do show any errors or problems.
    Edit:
    I was wrong accusing Flash Builder on this one! I've had two asset source paths that overlapped and apparently, Flash Builder can't handle that when you try to make a release build. Again, debugging always worked fine. I didn't get any warnings either, so it took me quite some time to even think that that might be an issue.
    Still, the pletheora of Flash Builder bugs remains!
    Found a new one with is also rather annoying recently;
    Open the local history of a file and try to copy some text from that file, you'll instantly get a java nullpointer, resulting in the fact that the text isn't copied to the clipboard.
    Edit2:
    That last edit was actually based on a premature thought of success. Unfortunately, the project still doesn't compile. There are no errors or problems whatsoever in neither of the library projects or the main project.
    Edit3: - Finally solved it!
    After re-installing FB4.7, thus overwriting the old installation with all it's SDKs, I figured that the merged SDKs might have been causing this issue.
    I've merged SDKs several times before using FB4.7 and it worked fine all the time, the absolutely ridiculous way Adobe forces us to update the AIR SDK with 4.7 is so prone to error, that I might have made a mistake this time though.
    So for everyone who struggles with this issue as well, make sure your SDKs are in order! Also check the version numbers in air-sdk-description.xml which is located in the AIRSDK folder.

  • Losing my embeded bullet symbol when I do Export Release Build

    I am using a bullet symbol in my Flex project as follows: 1) created a .swf in Flash with the fonts I want to use, including a bullet symbol (unicode 25CF).  I am using a .css to embed my .swf fonts for use in my project.  I am then using the bullet symbol inside a TextArea by assigning a string of text, including my bullet symbol, to the .htmlText property of the TextArea.
    e.g.
    private const BULLET_SYMBOL:String = "\u25CF";textArea.htmlText = "<font color='#00ff00'>"+BULLET_SYMBOL+"</font> Hello World."
    All works fine when I build for debug.  My little green bullet appears perfectly.  When I use Export Release Build..., my bullets are no longer there.  What can I do about this?

    So, even after setting up a new project, the problem didn't go away. Seems as if the problem sits within the libraries I'm using, though none of them do show any errors or problems.
    Edit:
    I was wrong accusing Flash Builder on this one! I've had two asset source paths that overlapped and apparently, Flash Builder can't handle that when you try to make a release build. Again, debugging always worked fine. I didn't get any warnings either, so it took me quite some time to even think that that might be an issue.
    Still, the pletheora of Flash Builder bugs remains!
    Found a new one with is also rather annoying recently;
    Open the local history of a file and try to copy some text from that file, you'll instantly get a java nullpointer, resulting in the fact that the text isn't copied to the clipboard.
    Edit2:
    That last edit was actually based on a premature thought of success. Unfortunately, the project still doesn't compile. There are no errors or problems whatsoever in neither of the library projects or the main project.
    Edit3: - Finally solved it!
    After re-installing FB4.7, thus overwriting the old installation with all it's SDKs, I figured that the merged SDKs might have been causing this issue.
    I've merged SDKs several times before using FB4.7 and it worked fine all the time, the absolutely ridiculous way Adobe forces us to update the AIR SDK with 4.7 is so prone to error, that I might have made a mistake this time though.
    So for everyone who struggles with this issue as well, make sure your SDKs are in order! Also check the version numbers in air-sdk-description.xml which is located in the AIRSDK folder.

Maybe you are looking for