Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

10.4: FileVault breaks some Automator Actions System 10.4
Tiger only hintI recently solved a problem I have been having with Automator for a while. When I run certain Automator actions (for example, when trying to rename Finder items) I get the following error:

AppleScript Error: Finder got an error: Can't get properties of alias "user:path:to:file". (error -1728)

It turns out that if you have FileVault enabled, many Automator actions break when you run them. My hunch is that this bug has to do with the way the system handles paths to your home directory when it is mounted through FileVault.

The solution is to either disable FileVault, or to simply copy the file(s) out of your home directory before running the Automator action on them, and then copy them back when you are done. What I don't understand is why the same Automator action worked when I created it months ago, but stopped working somewhere along the way.
    •    
  • Currently 3.00 / 5
  You rated: 5 / 5 (5 votes cast)
 
[8,864 views]  

10.4: FileVault breaks some Automator Actions | 7 comments | Create New Account
Click here to return to the '10.4: FileVault breaks some Automator Actions' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.4: FileVault breaks some Automator Actions
Authored by: beccles on Oct 24, '05 04:54:04PM

Thanks! This problem had been bothering me for months. The Finder script 'Replace Text in Item Names' would just not work. I'd posted several times to Apple Discussions and no one knew anything. I recently nuked my box, decided not to go with FileVault, and AppleScrpit works again. I never made the connection! How did you?

BTW this is my first post. I think it would be handy if I could see the original post I'm respoding to while I type this (memory of a goldfish...)



[ Reply to This | # ]
10.4: FileVault breaks some Automator Actions
Authored by: smeger on Oct 25, '05 10:42:42AM
I had to give a talk on Automator a few months ago and this drove me insane until I figured out what was happening. This post sounded like it'd let me work around it, but I wound up just creating a new, non-filevaulted user for my presentation.

The same issue was also preventing the "Get Finder Selection" functionality of both Quicksilver and Launchbar from working properly, driving me crazy for, well, about a year.

[ Reply to This | # ]
10.4: FileVault breaks some Automator Actions
Authored by: moritzh on Oct 25, '05 05:53:12PM
Yes, unfortunately you are right. I've had similar error messages in regular AppleScript programs (not via Automator) when referring to files in a FileVault, and of course I took me ages to find out the cause. There seems to be no way of avoiding them except for, as mentioned, simply not referring to files within a FileVault. As far as I know, Apple has been aware of this for a long time but doesn't seem to find it necessary to fix it. A little reminder or bug report by many people might have some effect...

[ Reply to This | # ]
10.4: FileVault breaks some Automator Actions
Authored by: svoida on Nov 02, '05 06:03:08PM

Anyone know if this was fixed in 10.4.3?



[ Reply to This | # ]
10.4: FileVault breaks some Automator Actions
Authored by: paole on Nov 23, '05 03:57:24AM

unfortunately: no. :(



[ Reply to This | # ]
10.4: FileVault breaks some Automator Actions
Authored by: cryptonomicon on Dec 03, '05 09:39:35PM

Yes, this appears to have been fixed in 10.4.3. They revamped how the path syntax is returned by the various Finder actions, which in the process seems to have fixed this issue.



[ Reply to This | # ]
10.4: FileVault breaks some Automator Actions
Authored by: cryptonomicon on Dec 04, '05 12:40:31AM

Nevermind... it is still broken. However, for some strange reason if you save an automator workflow as a Finder plugin it sometimes seems to work, despite FileVault being used. This is what made me think it had been fixed... not really sure what the conditions are for it to work or not as plugin.



[ Reply to This | # ]