FlashTmp() looks like a method to me. You sure there's no code in there? Lots of Sandbox Violation warnings are swallowed and harmless. My general rule is that unless it throws up the RTE dialog, it was just a warning. I think I would just explore why the app is in a bad state keeping mind that if there was a security violation thrown at one place and caught pretty far away, then lots of code might not have run that you expected to run.
Alex Harui Flex SDK Developer Adobe Systems Inc.<http://www.adobe.com/> Blog: http://blogs.adobe.com/aharui From: [email protected] [mailto:[email protected]] On Behalf Of Ken Dunnington Sent: Wednesday, May 20, 2009 1:56 PM To: [email protected] Subject: [flexcoders] AIR: Security sandbox violation: PNG trying to access .swf? Hi all, I'm getting some bizarre security errors in an AIR app, and I can't for the life of me make any sense of them. The most reproducible error looks like this: *** Security Sandbox Violation *** SecurityDomain 'file:///private/var/folders/8J/8J8HEVvxHMy7RVKw4iIqcE+++TI/TemporaryItems/FlashTmp0<file:///\\private\var\folders\8J\8J8HEVvxHMy7RVKw4iIqcE+++TI\TemporaryItems\FlashTmp0>' tried to access incompatible context 'app:/Main.swf' What's happening in the app is I'm taking a snapshot of part of the screen, then saving it to a temporary file until needed. Thing is, I don't get this error actually writing or reading the file, I get it after the file has been written, and I start scrolling a HorizontalList component that is completely unrelated to the thumbnail snapshot. I get it every time I click the scrollbar, but not while dragging. The error doesn't trigger the debugger, it just shows up in the console. What the heck is going on? I don't even know how it would be possible for this error to be generated as 'FlashTemp0' is just a PNG, not a SWF! What's more, often after these errors occur, switching states in my app will fail, and the UI will vanish (and by 'fail', I of course mean that no errors are generated and remaining pieces of the UI still partially work, but the app is now in an unusable state.) Sorry if this post is vague on details, this app is near the end of development, so I don't even know where to begin in terms of pasting example code. - Ken
