Flex Module throwing security sandbox violation

Question

I converted a standalone Flex app into a module. Now that it's a module, when I login (and call the backend services), I'm getting a security sandbox violation.

The login handler throws this fault String: 'Send Failed', with a more descriptive: 'Channel.Connect.Failed error NetConnection.Call.Failed: HTTP: Failed:url: 'http://myUrl:8080/AppManager/messagebroker/amf'.

Then the FB console throws an 'unhandled security sandbox violation error'.

Can converting an app into a module cause a sandbox violation?

Thanks for any helpful tips.

Because a Flex module must be in the same security domain as the application (SWF) that loads it, when you're using modules in an AIR application any module SWF must be located in the same directory as the main application SWF or one of its subdirectories, which ensures that like the main application SWF, the module SWF is in the AIR application security sandbox. One way to verify this is to ensure that a relative URL for the module's location doesn't require "../" ("up one level") notation to navigate outside the application directory or one of its subdirectories. — shaunhusain
^ that's from the adobe docs, also curious though does it make a request for the crossdomain.xml file, debugging with Firebug or Charles will probably help to see a bit more granular what is and what isn't happening — shaunhusain

mezmo mezmo · Accepted Answer · 2011-01-12T16:38:02

I'm making extensive use of modules and haven't run into this. There are memory issues I ran into that I had to fix by actually declaring an instance of the modules in the main modules...I didn't have to create an instance, just declare a variable to get the linkage right, then have all the other modules compile against that main module. Memory errors went away, and all the other modules were much smaller too.

Flex Module throwing security sandbox violation

1 Answers