I'm having the same problem, and am starting to think that it's caused by FileVault. If that's the case, it means that Adobe apparently didn't actually test anything on computers with FileVault turned on.
You are correct that SWF's in any folder that resides within a user directory do not load when FileVault is turned on. For example, the SWF generated when publishing /Users/<username>/Desktop/someFolder/someFile.fla or /Users/<username>/Documents/someFolder/someFile.fla will not load in Test Movie.
As a temporary workaround, you can save your FLA/SWF to another location like Macintosh HD/someFolder/someFile.fla since folders outside the user directory are not encrypted when FileVault is turned on.
We are investigating the issue and I will follow up on this post when we have a solution.
I am having the same issue when testing in flash cs5 (Error opening URL 'file:////.......) but I am NOT using FileVault.
I found out that if i save my fla on the desktop and then i test it it works but any file saved on my "data disk" will throw an error when tested.
I am really annoyed I paid a lot of money for a faulty sofware!!!
Please clarify the following:
What OS are you using?
What is your "data disk"? Is it a physical hard-drive on your machine or a mounted drive?
Do you have write permission for the folder?
What's the entire text of the error?
I was also having a problem with exporting the swf. for some reason in Text box will stop taking any input of just following numbers 5,6,7,8,9,0
And if i read do the fla which is exactly the same as before it will start working
any idea why this is happening
then i discovered if i change the acceptence text box text to _sans it starts working
I have no clue with this?
Any progress with this issue?
We are currently having difficulties publishing any FLAs that are housed on a network.
I was having the problem as well. Saving files to a different location is one thing, but none of my SWF-based panels were loading either (including the built-in Project panel). I followed the link on brendyn.com, where he'd posted an update with this solution from Adobe: http://kb2.adobe.com/cps/845/cpsid_84542.html It completely resolved the issue.