Skip to main content
satrugha
Participant
March 22, 2012
Answered

only main-app.xml and main.swf show up in apk package contents listing?

  • March 22, 2012
  • 2 replies
  • 1115 views

I'm using Flash Builder Pro 4.5 with Flex and Air to create an Android app.

I have a basic, start-up swf called main, but I keep my assets all in MainAssets. When I run the game in the Android emulation, it runs fine, but when I go to export it, only main-app.xml and main.swf show up.

Now I saw a forum mentioning dragging the assets into the bin-run (I haven't found an automated process for this yet) and the assets show up in Project > Export Release Build. That's all well and good EXCEPT my device says I'm running it in debug? (it has appName - Debug listed as the game name.)

If I go to File > Export and select Release Build, It will build a release version of my game HOWEVER only main-app.xml and main.swf show up, meaning no assets, no game.

So questions:

  1. Is Project > Export Release Build actually building a release or a debug? (I have to manually install apks since my device is belligerent and won't talk to FB)
  2. How do I get all my files to show up in File > Export? (I'd like to start writing my own xml loader but if I can't get it to pack xmls, it's a bit pointless)
  3. Can I automate this process somehow?

Thanks for all help.

I'm traditionally a C++ programmer so the automation awesomeness that Flash Pro did for me in packing and testing android apps did not compensate for how hard it was to code in.

This topic has been closed for replies.
Correct answer AirDoctrine2

In the projects that I've been compiling, FB doesn't copy most of the embeded files to the release folder when I do a Project->Export Release Build. Not sure why it doesn't copy the files during the export. It appears to be a bug in FB that has been around for at least a year or so.

I've just been working around this issue for a long time by doing the following:

Project->Export Release Build

Click the "Next" button.

On your Mac/PC manually browse to your project folder and copy your entire resource folder (MainAssets in your case by the sound of it) from your project's src folder to your destination release folder which should now have been created (e.g. bin-release-temp by default).

In FB click on the "Finish" button to finish building.

Hope that helps.

2 replies

AirDoctrine2Correct answer
Inspiring
March 23, 2012

In the projects that I've been compiling, FB doesn't copy most of the embeded files to the release folder when I do a Project->Export Release Build. Not sure why it doesn't copy the files during the export. It appears to be a bug in FB that has been around for at least a year or so.

I've just been working around this issue for a long time by doing the following:

Project->Export Release Build

Click the "Next" button.

On your Mac/PC manually browse to your project folder and copy your entire resource folder (MainAssets in your case by the sound of it) from your project's src folder to your destination release folder which should now have been created (e.g. bin-release-temp by default).

In FB click on the "Finish" button to finish building.

Hope that helps.

satrugha
satrughaAuthor
Participant
March 23, 2012

It does help. I'm surprised that this process hasn't been automated/corrected yet. I'm not sure why my phone was marking a build with this process as debug, but if this is the release version, then this is the way I'll go with it.

Thanks for the help