Export release build (desktop) settings?
Is there a configuration file somewhere that defines that the default "export release build" does? It must be driving mxmlc with something. Is there a way I can just get a look at that string? I'm working on my build system and trying to get all my fancy new compiler flags set right. It would be incredibly helpful to see exactly what that's doing.
I am building a Desktop AIR application.
Click Project > Export Release Build > Click Next
My screen shot is what you see AFTER I had clicked the first "Next" button.
In my screenshot the "Next" button is grey out because I had not yet input my password for the .p12 file. But that is irrevelant because you can click the "Customize Launch..." button after you click "Next" once.
Whether Desktop or Mobile does not matter. the "Customize Launch..." button appears for both
Similar Messages
-
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.
ThanksI 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 -
Export release build never completes
Installed Flash Builder 4.7 64 bit, now projects won't export. I complete the packaging settings and click finish then it just sits there with the progress bar moving. I left it going for an hour but nothing, not even an error message. In the task manager the disk activity drops to zero after 20 seconds.
Operating system is Windows 8 Pro, 6Gb ram.
Tried creating a new workspace and a new desktop project which exported ok. I then tried copying the source files into the new project and re-export release build, now the same result, just sits there doing nothing.
Message was edited by: mark21549Turns out it was Zone Alarm Anti Virus, uninstalled and all works ok.
-
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. -
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 -
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 -
Missing mxml:html/swf in Export Release Build
Hi,
I am using Flex 3 and have created several projects of which two have dropped the login.mxml (resulting html and swf) files when I export release build and publish it to my web server. I have compared settings in the projects where this does not happen and I can't find a reason for this behaviour. Its very annoying as I have to remember to manually copy the files from the flex_bin manually over. Anyone else encounter this or know why it might be happening?Hi,
I am using Flex 3 and have created several projects of which two have dropped the login.mxml (resulting html and swf) files when I export release build and publish it to my web server. I have compared settings in the projects where this does not happen and I can't find a reason for this behaviour. Its very annoying as I have to remember to manually copy the files from the flex_bin manually over. Anyone else encounter this or know why it might be happening? -
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 -
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
martinHi 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 -
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 : ADTMy 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 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>
<!-- Place non-visual elements (e.g., services, value objects) here -->
</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 3 - Export Release Build Feature
Just bought the Flex Builder 3 prof version and imported my
project from Flex Builder 2 to 3. All compiled OK and I see all
.html wrappers and swf (debug and release versions) in the bin
folder. However when I run the "Export Release Build Feature" only
index.swf (my main application file) along with its wrapper
index.html and my images directory gets copied to "bin-release"
folder. Not sure why remaining.swf files corresponding to the .mxml
files are not copied. Do I need to copy these manually???
Appreciate any help with this.
Thanks in advance.The problem is that:
all the images do not appear in the "Select the output files to include in the exported AIR or AIRI file" section of the Export Release Build. I see only 30 files with the rest of the files missing.
As a work around, what I did is manually copy all the resources/images from bin-debug to bin-release directory and then make the export release build. In this air package after installation, I see now all the images.
so, the original problem with flex builder not being able to include all the images in release build still persists.
thanks,
Sunil -
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...
-
Flash Builder + WTP = "Export Release Build" Broken
If I create a combined Flex/Java project and then click the "Export Release Build..." menu, then nothing appears to happen. If I just create a plain Flex project, then it works just fine.
I used the Eclipse Plug-in installer 4.0.1 (build 277662) for Windows XP SP3.
I am running the bundled 3.4.2 version of Eclpse and installed Subclipse and the WTP plugin.
I eventually looked through the Eclipse workspace log file and found the following stack trace. If anyone can offer me any suggestions on how to get this working I would appreciate it.
!ENTRY org.eclipse.ui 4 0 2010-11-11 15:54:01.577
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.NullPointerException
at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportReleaseVersionProjectAndLocati onPage.getDefaultOutputFolderPath(ExportReleaseVersionProjectAndLocationPage.java:485)
at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportReleaseVersionProjectAndLocati onPage.createLocationControls(ExportReleaseVersionProjectAndLocationPage.java:399)
at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportReleaseVersionProjectAndLocati onPage.createControl(ExportReleaseVersionProjectAndLocationPage.java:702)
at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:170)
at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportReleaseVersionWizard.createPag eControls(ExportReleaseVersionWizard.java:471)
at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:669)
at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:543)
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:583)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:500)
at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java :452)
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:3823)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2384)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2348)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2200)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:495)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:490)
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:193)
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:386)
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:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
Thanks,
Chris WardHi
I was able to reproduce this issue with Eclipse 3.6 and burrito build.
When I create a flex/java project I am not able to export the release build and the null pointer exception occurs.
But when I create the flex/java project with remote object service as LCDS export worked fine.
Also export of normal project is worked fine. I raised a bug http://bugs.adobe.com/jira/browse/FB-29046 for the same
I am attaching the logs here
ENTRY org.eclipse.ui 4 0 2010-11-17 10:52:09.360
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.NullPointerException
at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportReleaseVersionMainPageContent. getDefaultOutputFolderPath(ExportReleaseVersionMainPageContent.java:581)
at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportReleaseVersionMainPageContent. createLocationControls(ExportReleaseVersionMainPageContent.java:282)
at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportReleaseVersionMainPageContent. createControls(ExportReleaseVersionMainPageContent.java:193)
at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportReleaseVersionProjectAndLocati onPage.createControl(ExportReleaseVersionProjectAndLocationPage.java:188)
at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1226)
at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1218)
at org.eclipse.jface.wizard.WizardDialog$6.run(WizardDialog.java:1207)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1205)
at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:894)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:426)
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 org.eclipse.ui.internal.handlers.WizardHandler$Export.executeHandler(WizardHandler.java:9 8)
at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:274)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.jav a:508)
at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169)
at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.j ava:241)
at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
at org.eclipse.ui.internal.actions.CommandAction.run(CommandAction.java:171)
at org.eclipse.ui.actions.ExportResourcesAction.run(ExportResourcesAction.java:116)
at org.eclipse.ui.actions.BaseSelectionListenerAction.runWithEvent(BaseSelectionListenerActi on.java:168)
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)
Thanks and Regards
Swathi -
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.
Maybe you are looking for
-
Unable to get iTunes match setup to complete
I recently subscribed to iTunes Match but have been unable to successfully complete the setup process. I have read many other posts regarding initial matching troublingshooting and tried the following: -Sign in and out of iTunes Store -Disable and r
-
Please tell what to do if I see this error while opening an plan or while saving this plan?
Error messsge: the enterprise global already contains a table named "Enterprise Entry". Do you want to replace the table with the one from the enterprise global, replace all items with duplicates, rename the table in the project, or cancel opening th
-
ORA-00600: internal error code, arguments: [6122], [0], [4], [0], [], [], [
Hi All, I Got ORA-00600: internal error code, arguments: [6122], [0], [4], [0], [], [], [], [], [], [], [], [] today i check for Oracle knowledge but i can see only until 9i version. I am pasting my OS AND database version below Oracle Database 11g E
-
Why can't i see all the tabs in itunes store??
Hello. I am from Romania and I recently got an ipod nano 5th gen so i am very new at this.At first i used it on a different computer and everything was fine, then when i got home to my computer i noticed that i can't find the music,movies,podcast etc
-
Hi everyone, If someone can help me with this.. I have a mster table that is used by our billing software which is a non custom designed s/w. I still can work on the tables for that s/w but i do not want to modify any of them and get no references(se