File paths are broken on Golden Gate?

AppleScript
#1

This is not related specifically to Script Debugger:

Unless I’m missing something, path management in AppleScript is totally broken on Golden Gate.

Instead of volume name, paths now return “Data”. E.g. /Volumes/Data/Users/ or Data:Users etc. This breaks existing scripts because it looks like these paths are not understood anymore (by Finder, for example).

Also, NSFileManager in ASOC doesn’t understand these malformed paths. It does understand paths in their normal form where the volume name is present. But it means that paths obtained from standard AppleScript functions cannot be passed to NSFileManager.

After spending about an hour trying to understand this mess, all I know that scripts that worked for over a decade don’t work anymore. I wonder if anyone else encountered the same?

#2

P.S. Ok I think it only affects files that are not on the startup volume, but are on another volume where a bootable system is also installed. I still think this worked as expected before Golden Gate.

#3

Are you dealing with a Time Machine volume ?

#4

No.
Not dealing with Time Machine volume.

#5

Does an explicit coercion (... as POSIX path) resolve the problem? This would fall back gracefully on older systems.

#6

It doesn’t let me compile with as POSIX path:

Expected class name but found property

#7

Hello @leo_r :wave:

Please be patient if my answers are not correct… I’m not an expert like others (Mark or Shane for example) here. Besides I’m still using older systems but here are my thoughts:

Maybe you should try class furl (sorry I’m writing this on an iPhone because of that no real chevron syntax) instead or use the classic url methods in relation to NSFileManager. Maybe you didn’t do that and that’s why you can’t compile.

Good luck and happy scripting. Greetings from Germany :de:

Tobias

#8

Nah that’s not related. I vaguely recall using as POSIX path sometime in the past, but I don’t see it used in any projects now. as POSIX path can’t be compiled on either Tahoe or Golden Gate.

#9

My Apologies, I misdirected you.

POSIX path is a property, not a class. Something like this may work:

POSIX path of (... as POSIX file)

Can you show an example of the data value you are receiving. Data values have a 4-character class code that precedes the Hex data. I’m curious to see what class code has been assigned.

#10

Thanks @alldritt. We can consider this topic closed as it’s not worth the time trying to get to the bottom of it for any practical reason. Plus, I tested the same situation with clean new scripts, and I couldn’t even reproduce the issue I had with existing scripts.