The settings manager and/or flashplayertrust files make the sandbox rules 
LOCAL_TRUSTED instead of one of the other LOCAL_XXX sandboxes.  I think you 
have to specify locations to trust in that dialog.  AlwaysAllow option may be 
for internet hosted SWFs


On 8/3/10 9:52 AM, "Nick Middleweek" <[email protected]> wrote:






Hi,

Hopefully the Player Security subject hasn't scared you off but I'm stumped 
with an issue. When I'm creating a little demo app or any Flex app really, I'm 
accessing the local file system for an .xml settings file and a search will 
access a remote HTTP or Web Service so I'm accessing both local and remove 
resources.

I do a Release Build, test and it works.

I zip it up, send to my product owner and he gets a security error.

I've tried directing him to 
http://www.macromedia.com/support/documentation/en/flashplayer/help/settings_manager04.html
 to tick "Always allow", restart the browser, reload the flex app via the .html 
file but still no joy. Security error.

Does anyone know why this works on my machine but not his? Is it because I'm 
using the Flash Debug player?

Are there any rules around making a SWF be Security.LOCAL_TRUSTED ?

I'm on Vista Business, my PO is on Windows 7.


Cheers,
Nick





--
Alex Harui
Flex SDK Team
Adobe System, Inc.
http://blogs.adobe.com/aharui

Reply via email to