Question: We are creating an app that uses modules which are dynamically loaded into the main swf. The problem we run into, is that we are unable to load the modules located on a test server when we are debugging the main app locally. The error we get is "SWF is not a loadable module".

I looked this up and found out that we need a crossdomain file on the server that grants permission to load the modules from external locations. So we created a simple crossdomain file and put that on the server, but this does not seem to help.

Here's the crossdomain file:

```
<cross-domain-policy>
  <allow-access-from domain="*"/>
</cross-domain-policy>

```

We are loading the module via the ModuleLoader class and all default settings, no custom app domain etc. When we deploy the main swf onto the server we are able to load the modules without problems.

Any clues? Is the crossdomain file perhaps missing some settings?

**Update**: It seems that the external module is loaded successfully (I can verify in my HTTP sniffer) but fails to initialize when loaded in the main app. The error still is "SWF is not a loadable module)

Answer: 
Here is a proposed soultion from Adobe JIRA: <http://bugs.adobe.com/jira/browse/SDK-15393>
I agree that it could be an issue between local SWFs and remote SWFs. Try uploading your local file to a server (any server you have access to) or, if you've got a local Apache or IIS running, try accessing that SWF using <http://localhost/>. If that works, we'll know that the issue is in going between a local file and a remote file. If it doesn't than the issue is either with crossdomain.xml or in your code, which is less likely but we shouldn't rule it out just yet. If you do determine that the issue is with using a local SWF, then add the local folder in the Settings Manager (see macke's post)