Export Release Build Problem

I am using Adobe Flex Builder 3 on Windows 7.  When I got to export a release build to publish the project, the bin-release folder does not get all necessary files.  All of the .mxml files are not copied to the folder.  This just started happening out of the blue for some reason and had been operating properly prior.  If I select the option to view source files I can see the files that should have been copied by Extracting the zip file that contains the viewable source, but they do not copy on their own. 

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

Similar Messages

  • 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

  • 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

  • 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.

  • 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.

  • 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

  • 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

  • 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)

  • Exporting release build

    In flash builder I am targeting flash player 9 and use actionscript project.
    I see some strange behavior. I created my design in Photoshop CS3, then I imported .psd file in Flash CS3 and exported as SWC file. I added this SWC in Reference libraries in Flash Builder. If I run my project in Flash Builder - all is working and graphics objects are smooth and clean. But if I export release build, upload the SWF to server and run my website - I see jerky low quality graphics objects. Please help, any pointing very appreciated.

    problem solved, problem was in embeding on web with swfObject

  • 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

  • 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 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

  • 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.

Maybe you are looking for

  • Renew SSL key fail in WL Server

    We need to renew our certificate in the production environment. The new key is 2048 bit encrypted. When importing it to the keystore with "NO" password protection on the private key, the server ssl works fine. When I encrypt the file using wlkeytool

  • Airport Extreme 802.11n gone after firmware update

    Started Airport Utility earlier today, just to check a password. An Apple window came up offering new firmware, 7.1.1, I think. I usually accept these offers without thought, so I let the update run. Now Airport Utility cannot detect the Airport Extr

  • Preview Unavailable for this File?

    Need some help on this one.  I want to upload a file to Lightroom 5 and it will not work.  The program opens the file but then says "Preview unavailable for this file".  Since I had no problem uploading other photos in this catalogue, I don't underst

  • Transfered photos, now I can't delete them.

    So I've uploaded some pictures on my old computer and then, I've transfered my iTunes library to my new computer. But when I synced, there was still a copy of the same photo library from  my old computer and a new one with the same pictures in it. No

  • Error installing OBI EE on Dell XP

    Hi all, I am trying to install OBI EE on my laptop (Dell Lattitude 630 / XP). Right after clicking set up.exe I get a message that my platform is not supported and then it lists the supported platforms. Looking at this forum I saw some people having