And it's supposed to "just work" so there's no way to diagnose problems.
And it's supposed to "just work" so there's no way to diagnose problems.
Details: https://forums.developer.apple.com/thread/80174 (it had something to do with the preboot iirc, note that this wasn't on the beta but the actual release)
Cold boot login took over a minute on a 2013 MBP that runs Sierra just fine. Something was clearly hanging 60-75% through login and crashing the display server. Function keys wouldn't work until after first login. Can't change screen brightness, keyboard backlight always off, etc.
Only posts on Apple support forums were useless. Yes, I've run a disk check. No, a reboot didn't magically fix it. I've always done a disk check post-upgrade because the updater always seems to misplace >1k blocks in the filesystem after upgrading. The >console user login didn't work at all. Safe Boot looked like a broken powerpoint, is that supposed to happen?
I have no idea what I'm going to do with this update. I'm lucky Time Machine didn't garble my backup sparsebundle, which happens about every six months.
Also many problems with apps using the Java.Framework, such as JetBrains IDEs having no menus.
Newly installed AudioUnits plugins would not load until after a reboot (which is minor compared to the above).
10.13.2 beta seems to have resolved all these issues. I've not had a single freeze since installing this beta.