Forum user: gowiththeflow

Hi

What I did was check out the Flowplayer project source code, and make the change in the URLUtil file as described above.

Once the change is made, you would need to rebuild the project using ant, which would give you your very own flowplayer swf.

Obviously this isn't the same as the FP team would make this change (or a different one). You should also be mindful of licensing issues if you consider going down this route. I believe FP is licensed under GPL, which would presumably mean that your Air app would have to conform to a similar licence.

I didn't get anywhere with air security sandbox stuff. I don't believe that's the issue here.

Hope this is useful. FWIW I decided not to use FP for my air project in the end, opting instead to use adobe APIs directly.

After some further poking around, I've found that the error is caused by setting the current SecurityDomain (line loaderContext.securityDomain = SecurityDomain.currentDomain;
in PluginLoader). This is in turn done since the call to URLUtil.localDomain returns false.

The reason for localDomain returning false is that AIR prepends local path references with the app: URI scheme. Therefore I've been able to get FP working with AIR by adding the following check to URLUtil.localDomain:

if (swfUrl.indexOf("app:") == 0) return true;

I've validated this fix locally and it's worked great for me.

What are the chances of getting this patch into the next Flowplayer release?

Many thanks

Hi folks

Trying to get flowplayer working in an Adobe AIR html app, and so far failing.

When player initialisation is attempted, I get the following error in the player window:

300: Player initialization failed: SecurityError: Error #2142

I've been following the 'minimal installation' directions. I've added the FP swf and js files to the project, have made sure that both are packaged. I have included the js in the main html page, created the anchor container, and am instantiating the player as shown in the tutorial.

Looks like the above problem is some sort of Flex / Air security sandbox issue, but I've been unable to find anything concrete relating to it - has anyone else had it and / or solved it?

Any pointers appreciated.