SecurityError: Error # 2000: There is no active security context when importing an external SWF file

Question

I am trying to load a SWF file that contains an xml-based image gallery on the 25th frame of the timeline inside flash professional cs5.5 using actioncript 3. In doing so, I get this error "SecurityError: Error # 2000: No active security context". Below is the as3 code:

stop(); import flash.net.URLRequest; import flash.display.Loader; import flash.events.Event; import flash.events.ProgressEvent; function startLoad() { var mLoader:Loader = new Loader(); var mRequest:URLRequest = new URLRequest("../xml_gallery_2_852/XMLGALLERY2.swf"); mLoader.contentLoaderInfo.addEventListener(Event.COMPLETE, onCompleteHandler); mLoader.contentLoaderInfo.addEventListener(ProgressEvent.PROGRESS, onProgressHandler); mLoader.load(mRequest); } function onCompleteHandler(loadEvent:Event) { addChild(loadEvent.currentTarget.content); } function onProgressHandler(mProgress:ProgressEvent) { var percent:Number = mProgress.bytesLoaded/mProgress.bytesTotal; trace(percent); } startLoad(); 

Answer 1

Security errors are thrown when an operation is not allowed in the security environment in which the application is running. This may have several reasons: none of them try to access the local file from the application that was compiled using use-network=true .

EDIT

After reading your question, I came across the most likely reason, but in any case I will leave other information - this may be useful to other users.

You download the image gallery, which in turn downloads other files (XML), but the external SWF was compiled with the use-network option, and the FLA automatically starts as a local-trusted application when exporting from the Flash IDE. This, of course, is a violation of the sandbox.

You can test this by running SWF from a web server with a valid security policy - if I assume that your application should work then.

By the way, if you add an event listener to contentLoaderInfo to handle security errors, you can prevent your application from crashing and exit.

End edit

The error may be due to a small delay between the bootloader instance and the initialization of its security context. See this blog post for more details.

If this is the case, you should be able to properly get rid of the error by delaying the load request using setTimeout() or by moving the declaration of your loader outside the function block, i.e.

 var mLoader:Loader = new Loader(); function startLoad() { var mRequest:URLRequest = new URLRequest("../xml_gallery_2_852/XMLGALLERY2.swf"); mLoader.contentLoaderInfo.addEventListener(Event.COMPLETE, onCompleteHandler); mLoader.contentLoaderInfo.addEventListener(ProgressEvent.PROGRESS, onProgressHandler); mLoader.load(mRequest); } 

Declaring your loader as a temp variable is dirty anyway: the link is lost, but the event listeners you added to contentLoaderInfo keep it in memory, whether it is needed or not. This can cause serious memory leaks if you intend to download more than one file. You should always specify a link to your loader if you want to properly utilize downloaded content when it is no longer needed (using Loader.unload() ), and make the loader accessible for garbage collection (by deleting event listeners and explicitly after using the link on null ).

Answer 2

This is an old thread and seems to have already been answered, but there was another, obvious solution (which might or may not have helped here).

I could use this answer to rid me of sadness (I just went through it myself).

I uploaded images through the Loader class and continued to receive this cryptic message (I speak cryptically because it did not help me identify the problem) - SecurityError: Error # 2000: active security context

Solution - use the correct source path. I changed the directory name and forgot to update my code.

So, I called "src / pics / image01.png" in URLRequest ... However, I changed the "pics" directory to "img" and had to call "src / img / image01.png" instead.

If you get the "Error No. 2000" message, double-check your path and make sure that the file exists before anything else.