Adobe Export Release Build doesn't work - Mac OSX - Flex Builder 3

I have an AIR application i'm trying to release with flexbuilder.

Launching application has no problem ... bin-debug dir is correctly fille开发者_运维技巧d with my files.

But when i want to create the AIR file (export release fuild), AIR files content view is empty and bin-debug directory is never filled ...

Any idea ?

Thanks,

Yannick Grenzinger

---

I faced the same issue recently with the Export Release Build. I added the icon paths in the air app xml as below -

<icon>
   <image16x16>assets/icons/logo_16.png</image16x16>
   <image32x32>assets/icons/logo_32.png</image32x32>
   <image36x36></image36x36>
   <image48x48></image48x48>
   <image72x72></image72x72>
   <image128x128></image128x128>
</icon>

This caused the issue. Commented the above lines and it worked without any issues. Hope this helps.

---

I had the same problem. Seemed to be a problem with the XML config file for the application. Create a new MXML application, (something named different clearly). Copy and paste the code from the other app over. Bam, it works again! Hope this helps your problem.

---

When you export a release build; you are given the option to specify a directory. I believe this is named "bin-release" by default, a least for Flex projects. Are you sure you specified this correct directory?

The output of an AIR project export will be a .AIR ile which you need to install on your machine to run. Have you done that?

If your project has multiple application files, make sure you are exporting the proper one.

I'm unclear what you mean when you refer to the "AIR Files Content View."

---

Well, I just got the same issue!

Here's what I found out (even though I have not found a great solution for this yet). While exporting the release build, Flex Builder generates a directory named "bin_release" where all files to be included in the package are dumped. To fix my issue, so far all I have to do is to copy all the missing files into this directory before I click "finish" in the Export Release wizard.

Not a final solution but its a quick work around!