Depending on how you load them, some code might be trying to access them for
you The stack trace should give a clue.
This isn't an error on access. This is an error on load. The Loader never fires a Complete event. So that stack trace doesn't give any extra useful information. (For testing, we've boiled down this to a test app, so the only code is the loader code.)
What is the full text of the error? Is the Loader on the display list? I
think if it can't display at full size it may need to access the bits to
The Loader is on the display list before it is given a source urlrequest.
Interestingly, if we try two load two images at startup using two different Loaders, both attempts throw errors AND both images load. If we do this twice, but put delay between the first and second attempt, both attempts throw errors AND ONLY the first image is loaded while the second image load fails.
Console Output (note: main app is in domain1.com):
Post your test case. Does the app actually stop with the exception dialog
or does it continue on?
It's an error event, so it's doesn't bring up the exception dialog.
I'm working on getting a verson of the code I can post.
I don't know what your crossdomain.xml looks like, but try this:
<allow-access-from domain="*.yourdomain.com" secure="false"/>
<allow-http-request-headers-from domain="*" headers="*"/>
changing "*.yourdomain.com" to your actual domain, or just * if you don't care. the secure="false" is the important part, it helped me to resolve some non-https JPGs which would not load from a https hosted SWF.