I have had this issue countless times with my Flex applications. When I export a release build of my application, it is not able to load my initial configuration files and thus my application can't start. Everything works fine if I run the application from bin-debug folder. For this reason, I often have to deploy my bin-debug folder's contents which are much larger in size.
I am loading those configuration files through URLLoader. All paths being loaded at run-time are relative to the SWF's location. I have tried the compiler option
-use-network=true but it didn't help. The release version doesn't throw any run-time errors. I uploaded bin-release folder to my server and saw the HTTP requests in Firebug but none of those requests is loading the SWZ files or my configuration files. However, when I monitor the requests made by my bin-debug application, it loads all the RSLs (SWF files in bin-debug's case) as well as my config files.
So you can deploy the debug swf to the same url as the release swf and it will work?
Do you see anything when you use the release url?
Yes, the debug SWF works fine. When I run the release SWF, I just see the part of my application which shows while my XML files are supposed to be loading. Loading never actually happens so my application stays in the state which says "Loading configuration" or whatever I show there.
If you can show some UI, show a TextArea and output some logging info to it. For example output the URLs you are fetching.