Export release build error: couldn't cannonicalize path

Does anyone know what this could possibly mean? What path? Any clues gratefully received! Using Flex 3.

Further to this,
1. the app runs fine in debug mode
2. I have copied and run the app into FlashBuilder 4 - this time the Finish button just loops
3. I have recreated the app as a new project with new files, etc, but the same result
4. Just about to reinstall Flex

Similar Messages

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 errors

This just started happening to me in the last day or two. Every time I try to use Export Release Build, I get an error:
A folder named bin-release already exists with different case.
I checked my entire workspace folder and removed every bin-release folder, but the error persists. Is there any way I can get more info on what is annoying it? (Or better yet, a cure...)

I've been getting the same error. Here's my log:
!ENTRY com.adobe.flexbuilder.project 4 43 2010-09-07 15:03:56.806
!MESSAGE Uncaught exception in compiler
!STACK 0
java.lang.ArrayIndexOutOfBoundsException: 1129796362
        at flex2.compiler.PersistenceStore.readCompilationUnit(PersistenceStore.java:1568)
        at flex2.compiler.PersistenceStore.readCompilationUnits(PersistenceStore.java:1541)
        at flex2.compiler.PersistenceStore.read(PersistenceStore.java:958)
        at flex2.compiler.CompilerAPI.loadCompilationUnits(CompilerAPI.java:4856)
        at flex2.compiler.CompilerAPI.loadCompilationUnits(CompilerAPI.java:4835)
        at flex2.tools.oem.Application.loadCompilationUnits(Application.java:706)
        at flex2.tools.oem.Application.recompile(Application.java:1071)
        at flex2.tools.oem.Application.compile(Application.java:819)
        at flex2.tools.flexbuilder.BuilderApplication.compile(BuilderApplication.java:344)
        at com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder$MyBuilder.mybuild(A SApplicationBuilder.java:276)
        at com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder.build(ASApplication Builder.java:127)
        at com.adobe.flexbuilder.multisdk.compiler.internal.ASBuilder.build(ASBuilder.java:190)
        at com.adobe.flexbuilder.multisdk.compiler.internal.ASItemBuilder.build(ASItemBuilder.java:7 4)
        at com.adobe.flexbuilder.project.compiler.internal.FlexProjectBuilder.buildItem(FlexProjectB uilder.java:480)
        at com.adobe.flexbuilder.project.compiler.internal.FlexProjectBuilder.build(FlexProjectBuild er.java:306)
        at com.adobe.flexbuilder.project.compiler.internal.FlexIncrementalBuilder.build(FlexIncremen talBuilder.java:157)
        at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:627)
        at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
        at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:170)
        at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201)
        at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:253)
        at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
        at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256)
        at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:309)
        at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:341)
        at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:140)
        at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:238)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Export Release Build error

I am exporting AIR project and getting the following error after providing a certificate:
"Error occurred while saving the project settings: "default" build target cannot be found for the selected project."
I am using FB 4.5.
Thanks

I get this error as well everytime I create a mobile project in the lastest version of Launchpad, import the resulting files into Flex Builder 4.5 then try to export the project as a signed AIR desktop app. Exporting Release Build to a mobile target device works fine however.
Here is my log file as well:
!ENTRY com.adobe.flexbuilder.project 4 43 2011-09-09 17:33:29.640
!MESSAGE Failed to get build target settings: default
!STACK 0
java.lang.Exception
     at com.adobe.flexbuilder.project.internal.FlexProjectCore.createErrorStatus(FlexProjectCore. java:1009)
     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.project.ui.utils.ProjectBuildPackagingUI.doApplySettings(ProjectBui ldPackagingUI.java:754)
     at com.adobe.flexbuilder.project.ui.utils.ProjectBuildPackagingUI.applySettings(ProjectBuild PackagingUI.java:781)
     at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportReleaseVersionBuildPackagingPa geContent.saveSettings(ExportReleaseVersionBuildPackagingPageContent.java:131)
     at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportReleaseVersionBuildPackagingPa ge.saveSettings(ExportReleaseVersionBuildPackagingPage.java:84)
     at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportReleaseVersionWizard.performFi nish(ExportReleaseVersionWizard.java:144)
     at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:811)
     at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:430)
     at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
     at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234)
     at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
     at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657)
     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.Widget.sendEvent(Widget.java:1053)
     at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657)
     at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
     at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
     at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
     at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
     at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
     at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
     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:369)
     at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     at java.lang.reflect.Method.invoke(Unknown Source)
     at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
     at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
     at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
Update:
     As a work around, I tried to export it as an unsigned airi, then manually signed it with ADT using a self signed certificate and it worked perfectly...
Message was edited by: Jason Woodcock

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.

Exporting release build on mac "GL pipe is running in sofware mode" error problem

Hey guys, i was having problems with the uploading an app to the Apple appstore because of the new rule for 64bit apps so i had to recompile all the anes and whatnot.
After having all the anes 64bit compatible, when i go to "Export release build" i get this error
"WARNING: GL pipe is running in software mode (Renderer ID=0x1020400)"
Only for the iOS version. The Android APK file compiles without any problems...

Hi Bigmachini,
According to my solution, what about your issue now?
If you have been solved the issue, would you mind sharing us the solution here? So it would be helpful for other members who get the same issue.
If not, please let us know the latest information about it.
@Malik, could you please tell me if you try to check your issue by the above suggestion as I said?
If no, please try the above suggestions to check this issue and then tell me the latest message about this issue.
>>The error mostly occurs when debugging ADO.NET or database function calls. If code is run without debugging then there is no issue at all.
You could also try to copy your project and then debug your project in debug mode on a another machine you install same Windows 10 OS check this issue again.
Best Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Export Release Build on Flash Builder 4 Beta 2

Hi Everyone,
I have a Flex 4 project that is organized as a main app project with several related projects that are linked in, along with several libraries that get included (I use granite dataservice and tweener, among others). The project runs fine when I do a normal build, I have deployed the resulting swf independently on a web server and its working fine.
Now, whenever I try to do 'Export release build' from the Project menu, the resulting release build doesnt run at all, and it crashes with weird errors, like for example, it first crashes because of a null reference in the partAdded method in one of the components I created, when I removed that component completely it crashed because of a type coercion error on one of the data service objects, and this goes on with all sorts of errors that never existed in the normal 'debug' version not built with the export option.
So I have two questions:
Does anyone have any clue what might be wrong? I would have posted examples but it looks to me like an application-wide anomaly, maybe because of it not loading the libraries or the resources correctly? I tried both build path options or merging sdk libraries into the code or using runtime libraries, didnt work, not sure if it is related.
What exactly does 'Export release build' add for me? is the release build faster than the normal one?
Thanks a lot.

Hi,
A release build optimises the compile,(no debugging code etc). The swf will be a little quicker and a lot smaller. If you are getting null pointers and data service issues maybe something in your create order is a bit out. If you have an idea of what the offending component may be see if you can set its creation policy. This would be my first thought the other could possibly be some sort of local versus network issue on the release build.
David.

Can't Export Release Build for AIR app...

Flash Builder 4.7 won't let me export a release build for any AIR apps at all...
It started when I wanted to make some changes to an old AIR app. Couldn't even run it in the debugger, so I updated the AIR SDK (using instructions found here: http://helpx.adobe.com/flash-builder/kb/overlay-air-sdk-flash-builder.html and here: http://helpx.adobe.com/x-productkb/multi/how-overlay-air-sdk-flex-sdk.html )
So after doing all that, and making some other changes, I finally got my AIR app to run in the debugger in Flash Builder 4.7. Made the changes I wanted to make, then tried to Export Release Build... Kept giving me a "Password Incorrect for this certificate" error whenever I tried it -- but it would never let me enter a password. I went to Project | Export Release Build, and on the first screen there, I would click "Next" and it would jump straight to compiling, skipping over the screen where you're supposed to be able to enter the certificate info and password.
Figured maybe because it was an old AIR project, that was causing the problem. So I started a brand new AIR project -- very simple one with just a <s:Label> inside a <s:WindowedApplication>. Went to Project | Properties | Flash Builder Packaging and created a brand-new self-signed certificate (which seemed to work) but again upon trying to export the release build, it wouldn't let me get to the screen where you enter the password. Clicking "Next" from the first screen on Project | Export Release Build just jumps straight to compiling and (of course) it gives me the Incorrect Password error, because it never gave me a chance to enter the password.
So what is going on here? Why can I not export any release builds for any AIR projects? This is extremely frustrating -- Flash Builder 4.6 never gave me these kinds of problems. What can I do to fix Flash Builder 4.7 so it will work properly with AIR projects?
Thanks,
L.

Hi,
I think something's wrong with either your FB 4.7 installation, or how you updated the AIR SDK. I just walked through the exact steps you listed (except I already had the AIR SDK overlayed) and I can build a desktop AIR app without issue. I get prompted for the password and everything.
I wish I had a better answer, but I'd suggest uninstalling and re-installing FB 4.7, be sure to remove preferences as well. Then before you update the AIR SDK, try building an AIR app with the base SDK that's included in 4.7. If you can get it to compile and prompt you for the password, then it's the way you overlayed the SDK that's messed something up.
Make sure you download the correct AIR SDK that's specific to Flex. On this download page: http://www.adobe.com/devnet/air/air-sdk-download.html is a reference in small print that says: Note : Flex users will need to download the original AIR SDK without the new compiler. Mac Windows. Make sure it's that version of the SDK (without the ASC 2.0 compiler). Then try overlaying the SDK again and see if that works.
I can definitely confirm that what you are experiencing isn't the norm, and that you can get the latest AIR SDK to work with FB 4.7
Good luck!
iBrent

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

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.

Export release build from WAMP-2-LAMP questions

Having some difficulties with exporting a release build to move onto a linux host. Looking for a better solution that will ease moving the code (build) to Prod env/version.
Other than the Flash Builder breaking when I start changing the server and path values that reflect the linux paths - I'm unable to export a release with the errors.Is it a build-time thing that it needs all this config - or is it in the release (post-build) that I do all my config edits?
Am I going about this the right way ? - or is there an easier way to export a release with the server settings as a config file - or a way I can just have one version in FB rather than trying to hack a production release to linux from windows?
Using the PHP services generated by FB - a folder called .model has the service config file for all the services - XYZ.fml
ie
    <annotation name="ServiceConfig">
      <item name="PHP_RELATIVE_LOCATION">XYZ/services/HactionService.php</item>
      <item name="PHP_SERVER_ROOT">C:\Program Files\Zend\Apache2\htdocs</item>
      <item name="DEFAULT_ENTITY_PACKAGE">valueObjects</item>
      <item name="PHP_SERVICES_FOLDER">C:\Program Files\Zend\Apache2\htdocs\XYZ\bin-debug\services</item>
      <item name="PHP_LOCATION">C:\Program Files\Zend\Apache2\htdocs\XYZ\services\HactionService.php</item>
      <item name="LINKED_FILE">HactionService.php</item>
      <item name="PHP_SERVER_ROOT_URL">http://localhost/</item>
      <item name="ABSOLUTE_ENDPOINT">http://localhost/XYZ/bin-debug/gateway.php</item>
      <item name="PHP_CLASS_NAME">HactionService</item>
    </annotation>
noticed the amf_config.ini file and that has linux paths for Zend - and I think that's ok - but the paths are reverse for on and not the other.
webroot =C:/Program Files/Zend/Apache2/htdocs
zend_path = C:\apache\PHPFrameworks\ZendFramework
Details - Win7, FB Beta 2, WAMP
martin

Hi Martin,
   Below are the steps to do an export release build and deploy the same on to any required target server (in your case MAMP)
Export release build of the project with the existing server settings:
1. Do export release build of the project.
2. zip the bin-release folder contents into say <xyz>.zip
3. upload xyz.zip to the target server and unzip its contents to /wwwroot/<xyz>/
Additional configurations and installations:
1. Zend installation: Your current local webroot would have a folder called ZendFramework, zip it and upload it to your server.
   Unzip the framework in your web root. If Zend Framework is installed in a location other than webroot, then you would have to update the amf_config.ini file. The amf-config.ini file will be found in the <xyz> folder
-    Uncomment and modify zend_path variable to the absolute path of the Zend framework directory.
-    Set amf.production to true.
-    Update webroot with the absolute path to the web root on the server
2. Ensure that any of the php services used by the application is already deployed on the server.
     Ensure that the same directory structure is maintained for the services deployed.
Hope it helps.
Regards,
   Latha

Export Release Build Flash Builder 4.5 fails to load over the web.

Exported Release Build Application fails to load over the web. You can reproduce using the following steps:
1. Create New Flex Project in Trial Flash Builder 4.5.
2. Use the default Flex 4.5 sdk.
3. Configure as a web application.
3. Place the following MXML code in the main application file:
<?xml version = "1.0" encoding = "utf-8"?>
<s:Application xmlns:fx = "http://ns.adobe.com/mxml/2009"
xmlns:s = "library://ns.adobe.com/flex/spark"
xmlns:mx = "library://ns.adobe.com/flex/mx"
minWidth = "955"
minHeight = "600">
<fx:Declarations>

</fx:Declarations>
<s:TextArea text = "Hello World!" width = "100%" height = "100%">
</s:TextArea>
</s:Application>
3. Save the main application file and Export Release Build to bin-release.
4. Place all files in bin-release on IIS web server in a web accessible location.
5. Go to the web accessible location in any browser with newest flash player and view the application's html page.
Actual Results:
Flash movie appears blank. Context menu shows Movie Not Loaded. Network traffic shows application main swf downloaded. Framework dependent swfs not downloaded.
Expected Results:
Movie loads. Hello World! appears in text box. Context menu does not show Movie Not Loaded. Framework dependent swfs downloaded.
Workaround (if any):
Deploy on an Apache web server.
The tests were run on IIS 7.x (7.0 for one, and 7.5)
Flex application was built using Flex 4.5.0 SDK pre-bundled release (built-in flex 4.5 with Flash Builder 4.5 trial) on Mac OS X 10.6.7 (10J869)
Flash Player 10.3.181.14
Example failing website:
http://staging.ibenergy.com/Test.html
Any idea as to why my exported release build fails? Any help would be appreciated.

Just tried this out on an IIS server with Flash player 10.3.181.14 - it worked.
Are you using the release version of Flash Builder 4.5 with the release version of Flex SDK (not a prior SDK build)?
The URL you mentioned gives me a 403 forbidden error.
-Anirudh

Flex Builder 4 Export Release Build fails on OSX

Flex Builder 4, SDK 4.1.0.16076
When I choose Project->Export Release Build, or Export Release Build from the Export context menu, nothing happens on teh interface, but I see the following error in the log. Any thoughts on solution or workaround?
Thanks
D
!ENTRY org.eclipse.ui 4 0 2011-05-25 14:54:44.886
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.NullPointerException
at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportReleaseVersionProjectAndLocati onPage.getDefaultOutputFolderPath(ExportReleaseVersionProjectAndLocationPage.java:312)
at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportReleaseVersionProjectAndLocati onPage.createLocationControls(ExportReleaseVersionProjectAndLocationPage.java:297)
at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportReleaseVersionProjectAndLocati onPage.createControl(ExportReleaseVersionProjectAndLocationPage.java:501)
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:734)
at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:606)
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:1669)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1693)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1678)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1421)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3657)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3240)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
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:369)
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:620)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
at org.eclipse.equinox.launcher.Main.run(Main.java:1408)

looks like this is same as http://bugs.adobe.com/jira/browse/FB-29046 -- export works if turn Application Server in Properties to None/Other rather than J2EE... that bug report was closed as unreproducible. Looks like its still out there in the wild...

Export Release Build

When I export release build in FB 3, if I leave "Enable view
source" unchecked, I get the error message:
quote:
Flex Builder could not publish the project source: the
application file "Main.mxml" was not found.
I click OK, and the project exports just fine. I shouldn't
get this error if I don't enable source view, right?

After trying for ages just created a new flex project and
copied all the code across to the new project. But didn't use the
old app-xml file used the one for the new flex project and the
icons worked.

Export Release Build stopped working on Flash builder 4.0.1

Does anybody else have a problem with "Export Release Build..." with the new Flash builder version ?
I'm selecting the option through the menu, and nothing happens.

Same here the error log of eclipse:
!ENTRY org.eclipse.ui 4 0 2010-07-05 11:25:51.796
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.NoClassDefFoundError: com/adobe/flexbuilder/exportimport/releaseversion/ui/ExportSigningPage$1
    at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportSigningPage.createControl(Expo rtSigningPage.java:117)
    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:3880)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473)
    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 com.adobe.flexbuilder.standalone.FlexBuilderApplication.start(FlexBuilderApplication.java :109)
    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(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    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)

Export release build error: couldn't cannonicalize path

Similar Messages

Maybe you are looking for