Error #3764: Reloading a SWF is not supported on this operating system.

[Zinder 0 Likes (Newbie)]

I have some issues reloading external swf-files.

I know it is a known issue and there is a lot written about it, but I still didn't manage to solve it.

 

This is the simple-code I use:

var m_oLoaderContext:LoaderContext = new LoaderContext (false, ApplicationDomain.currentDomain, null);
m_oGameLoader = new SWFLoader("externalcontent.swf" + "?newfile=" + Mah.random(), 
                        { name:"gameloader",
                          // autoDispose: true,
                          autoPlay:false,
                          centerRegistration:false,
                          x:0, y:0,  
                          scaleX:1, scaleY:1,
                          container:this,
                          noCache:true,
                          //onError:f_LoaderError,
                          onComplete:f_LoaderComplete,
                          context: m_oLoaderContext } );
m_oGameLoader.load();

The as3-Loader-class gave the same error at first, but I solved it adding the newfile-parameter + cacheResponse/useCache-properties:

m_oLoader = new Loader();
m_oLoader.visible = true;

m_oLoader.contentLoaderInfo.addEventListener(Event.COMPLETE, f_NativeLoaderComplete, false, 0, true);
//m_oLoader.contentLoaderInfo.addEventListener(IOErrorEvent.IO_ERROR, f_NativeLoaderError, false, 0, true);

var request:URLRequest;
request = new URLRequest();

request.url = p_sPad + "?newfile=" + Math.random();
request.cacheResponse = false;
request.useCache = false;

m_oLoader.load(request, m_oLoaderContext);

In the swfloader I allready diabled cache and added the newfile-paramter, but this doesn't do the trick.

I'm using Adobe Air SDK 14.0.0.73, but also tried some other versions like 3.7 / 3.8, with the same problem.

 

Is there something I'm missing?

[Carl 11,325 Likes (Superhero)]

Sorry, I'm not all that familiar with the latest Air bugs / issues. From a quick google search this seems to be quite a common error and a bit of a hassle.

 

Did you try passing your URLRequest into the SWFLoader?

var request:URLRequest;
request = new URLRequest();


request.url = p_sPad + "?newfile=" + Math.random();
request.cacheResponse = false;
request.useCache = false;


m_oGameLoader = new SWFLoader(request, 
                        { name:"gameloader",
                          // autoDispose: true,
                          autoPlay:false,
                          centerRegistration:false,
                          x:0, y:0,  
                          scaleX:1, scaleY:1,
                          container:this,
                          noCache:true,
                          //onError:f_LoaderError,
                          onComplete:f_LoaderComplete,
                          context: m_oLoaderContext } );

[Jakob Sternberg 5 Likes (Newbie)]

What type of AIR app are you compiling (Desktop/Android/iOS) ?

[Zinder 0 Likes (Newbie)]

Passing the URLRequest into the SWFLoader didn't do the trick ...

 

@squadjot: it's a known iOS-issue, and solvable as shown above with regular Loader-class, but not working for SWFLoader-class.

 

For the project I'm working on right know I switched to the Loader-class, but I still want to know how to solve this problem

[Giovani 2 Likes (Newbie)]

Maybe not the best aproach, but it may help you:

 

loading/core/LoadItem.as

 

change the line ~85 

 

from:

request.url = parsedURL

to: 

request.url = parsedURL+"?dieIOS="+getTimer(); 

and also don't forget to import it:

import flash.utils.getTimer;

[Keyda 0 Likes (Newbie)]

Please update this thread, can anyone answer?

[Carl 11,325 Likes (Superhero)]

Hi Keyda,

 

As you can see this issue hasn't been relevant to any users in about 2 years.

We have been sunsetting our Flash products and as such our support is really only focused on mission-critical bugs (of which there are none that we know of).

It's been about 3 years since we've done any development for Flash.

 

FWIW SWFLoader pre-dates AIR by a few years – it was never intended for a mobile environment.

We just don't have the resources to keep on top of AIR or anything ActionScript based.

 

You can read more here: http://greensock.com/forums/topic/13924-question-about-this-forum/

 

Hopefully you can get by with the solutions offered above.