Unable to export

Right click on the project folder > Refresh.

Then click on Project > Clean.

Thats all. This works for me.

Hey guys,

haha, ok, so this is the easiest solution ever!!

1.) First, delete the .project file (for web app or mobile app)

2.) Then delete any desktop.ini files (you need to view all files for this or use some app like WinRar or an FTP client, just something that shows all the files).  Delete all references for the desktop.ini file(s) but ONLY for what your using in your project (like your API, project folder, etc, Windows uses those so just delete the ones in your project folders).

3.) Then close Flash Builder, open it, do a Project -> Clean, then try to publish it.  Worked like a charm for me, if you still see that error then you more than likely have a desktop.ini file still sitting somewhere

Hope it helps,

Isaac

I came across the same problem and none of the suggested solution helped. However, I stumbled across an interesting log entry. There was a Java access right exception whilst trying to copy .picasa.ini (I'm using the picasa picture viewer to view image resources) from one of the linked resource folders into the bin-release-temp folder. After cleaning up all .picasa.ini files I could export a release build again.

It seems the export release build feature is very sensitive to files in the project directories not belonging to FB or the project. As for now I do not use any other software on files in my project directories to avoid this situation.

para todos los que le sucedio esto, a mi me sucedio con flash builder 4.5, lo raro es que exporte y genere varios proyectos y todo bien no se el bug donde es pero lo que supuce es que si ya antes me funcionaba deberia funcionar ahora asi que exporte en fxp todos mis proyectos y elimine la carpeta que se encuentra en C:\Users\Miusuario\Adobe Flash Builder 4.5 abri flash builder y logicamente todas sus configuraciones se borraron importe nuevamente mis fxp y todo de lujo, espero que si alguien le pasa lo mismo esto lo pueda ayudar bye me disculpan por la traducción al ingles la hice en google translator no se mucho ingles

I apologize for the English translation on google I did not know much English translator

for all that happened, happened to me with flash builder 4.5, the strange thing is that exports and generate multiple projects and not so good bug where it is but what is that if you supuce I worked before so it should work now fxp to export in all my projects and delete the folder located at C: \ Users \ myuser \ Adobe Flash Builder Flash Builder 4.5and logically I opened all your settings will be erased and re-imported my entire luxuryfxp, I hope that if someone it's the same this can help bye

Had the same problem, found a solution, its caused if RSL's are referenced/used by the main project.

posted the details of how to implement it on my blog

Found details of the solution here

The solution, if the problem occurs when using RSL's, is detailed in the following Post: http://forums.adobe.com/thread/732325

by eggsWurzel

Flash Builder 4 (v 4.0.1.277662) fails, when trying to do a release build with the following simple project setup: - Flash library project with a simple test class (using the 3.5 Flex SDK which ships with FB4) - Flex project with simple mxml-application (using the same SDK)   The Library is linked as RSL When you try to export the release build of the project, you´ll get an unspecified error. In the log file, you can found: java.lang.NoClassDefFoundError: flex2/tools/oem/OEMException$CircularLibraryDependencyException With some google search, I found out, that the error occured with FB 4 beta und should be already fixed. That´s for sure true with SDK 4.0 oder SDK 4.1, but not SDK 3.5 (remember: it´s the version, which ships with the FB itself !!!). After scanning the jar´s of the SDK 3.5 and 4.0, I found out, that the following 3 files are missing in the flex-compiler-oem.jar in SDK 3.5: - OEMException$CircularLibraryDependencyException.class - OEMException.class - OEMException_en.properties Adding these files to the jar of the 3.5 SDK, the release build will be successfully exported. We were absolutely disappointed after realizing this issue. This has cost a lot of working time and was frustrating too. Is there another way to get this working, without changing the SDK files?

I am going to try this solution. Will post back if successful

Hi,

If Asier's suggestion does not help your particular case, please feel free to export your project and email it (minus the file extension to get past the firewall) to ccampbel@adobe.com and I'll take a look.

Thanks,

Chris