File copying defaults to file cloning available only on APFS formatted disks. Fixed various crashes, exceptions and incompatibilities when running on macOS 10.13 (High Sierra).
Other minor fixes and improvements.
I did install the update, but I’m not running HS, so I can’t test.
The latest version of macOS, High Sierra (10.13), has been released, and there are a series of bugs to look out for. Several involve AppleScriptObjC, so if you don’t use it — or any libraries or applications built with it — you will not be affected. If you do, there are coding workarounds.
enum NSNotFound. This is most commonly used when getting the index of an object in an array: a result of NSNotFound means what its name implies. In 10.13.0, NSNotFound is returning the wrong value.
Code that returns the frames of things like views, which in Objective-C are normally returned as type known as a struct. The specific struct is NSRect. Because AppleScript does not support the concept of structs, they are bridged to records. But in 10.13.0, NSRects are bridged to lists instead.
Methods that take multiple parameters with a trailing nil, or missing value in AppleScript. These are methods like arrayWithObjects: and dictionaryWithObjectsAndKeys:. I suspect these are rarely used — there are simpler alternatives — but in 10.13.0 they are no longer supported. The best solution is likely to be to use the alternative methods, such as arrayWithArray: — the way support for all instances has been removed suggests this might be a deliberate decision.
Click on the above link for details and fixes.
Many, or even most, of the members of this forum probably don’t write much ASObjC, but you may use ASObjC scripts written by @ccstone, and to a lesser extent, by myself. I am not aware of any of these scripts (posted in this forum) that are broken under High Sierra, but then I haven’t tested any of them.
If you are running High Sierra and encounter failed or strange script results, please post a reply here, with a link to the topic where the script is posted.
Since many people use Keyboard Maestro to add or customize keyboard shortcuts for menu commands, David Sparks notes a High Sierra-based change for the Print to PDF command. Previously, in a Print dialog was a Print to PDF option, and in System Preferences > Keyboard > Shortcuts, a keyboard shortcut could be created for this menu item.
In the past, the command was displayed as
Print to PDF…
but in High Sierra it’s now just Print to PDF (without the ellipsis). This means a shortcut in System Preferences or in any reference to the command anywhere needs to have the ellipsis removed (the …).
The Select Menu action allow you to specify multiple options separated by a vertical bar (eg Show|Hide) to allow for toggling or varying menus. They will also ignore the difference between three dots (…) and an ellipsis (…) so you do not have to worry which one the menu uses.
Alternatively, you can start the name with an ^ and use a regular expression to match the menu.
I’m seeing a lot of that. You might be interested to know that even Shane Stanley is waiting until at least the .1 version of High Sierra is released, and he, by his own statement, is known for being an early adopter of macOS upgrades.
There are a lot of High Sierra complaints on the AppleScript Users List.
Another reviewer recommending to wait to .1 or .2 update.
I think the vast majority of people who decide to upgrade on day one will be essentially fine. But if it’s at all possible for you, you should wait for version 10.13.1 or 10.13.2 to update to High Sierra.
Aside from the fact that you’ll keep getting security (and Safari) updates in Sierra, I make this recommendation for three reasons:
The number of user-facing improvements is small. The Photos app gets the biggest overhaul, and it’s a good one, but otherwise you’re not missing very much.
Some things just aren’t done. APFS won’t work on Fusion Drives. External graphics support is usable but not finished. iMessage on iCloud isn’t here yet. The new Metal-powered windowserver is still intermittently buggy.
Even with fully finished, bug-free features, Apple has been clear that these are foundational updates. Meaning: cool, user-visible stuff will be built on top of them in future releases, but that stuff isn’t here yet.
I’m glad the upgrade has worked well for you Tom. Would you mind sharing the issues that it solved for you?[quote=“Tom, post:14, topic:7194”]
But don’t forget the security issues that are being fixed in 10.13 but not in previous systems.
One was a lag in the Finder that occurred (apparently) randomly, accompanied by something that appeared like a memory leak to me. Finder windows took 20s or so to become frontmost when clicked, and Finder was consuming a two-figure amount of memory at those occasions. I think it was related to the iCloud sync, because most of the time it was OK after killing cloudd. (But I might as well be wrong, since some months ago I said Dropbox was the culprit. Anyway, it is gone now.)
The second one was a continuous auto-destruction of the pbs preferences (the pbs.plist file). This is the file where all your shortcuts for the Services are stored. (System Preferences > Keyboard > Shortcuts > Services).
Each time I changed a shortcut everything has been reset to the defaults. You imagine the annoyance!?
I worked around it by tracking any changes to that file by Hazel, so I could restore it. Furthermore some shell commands like /System/Library/CoreServices/pbs -flush en seemed to be useful, before touching any shortcut.
I was referring to the last “supplemental” update that covered a key chain vulnerability present not only in HS but also in Sierra and Capitan. It was first only released to HS (not to previous systems), but it seems in the meantime it has been released also to the legacy systems.
Not sure though if it really has been released to all systems.
To be clear, I’m not for, or against, any macOS version in general. My evaluation is primarily based on whether or not there is a compelling reason to upgrade, and whether or not the new version breaks any of my essential workflows.
That’s why I keep asking you guys who have upgraded what your experience/evaluation is so far.
So, I’d love to hear/see why you think “High Sierra is still way better than Sierra (and El Capitan)”.