Apple seeded the second beta of macOS High Sierra 10.13.4 to developers earlier this week, but it appears an updated version of the second beta was just released this afternoon.
The original beta had a build number of 17E150f, while the new update available today from the Developer Center lists a build number of 17E150g. It's not clear why Apple has released an updated version of beta 2, but the new beta is also available for public beta testers.
Registered developers can download the beta from the Apple Developer Center or through the Software Update mechanism in the Mac App Store with the proper profile installed.
macOS High Sierra 10.13.4 beta 2 didn't introduce any major new features, but it did change "iBooks" to "Books" to mirror changes made in iOS 11.3.
The update includes bug fixes and performance improvements for issues that weren't addressed in macOS High Sierra 10.13.3, and it offers support for some features that are also available in iOS 11.3, like Messages on iCloud, which uploads all of your iMessages to the cloud. It will also support Business Chat, a feature coming when iOS 11.3 and macOS 10.13.4 are released to the public.
macOS 10.13.4 also includes the smoke cloud wallpaper that was previously only available on the iMac Pro, and it introduces a warning when opening up a 32-bit app as part of an effort to phase them out.
In the future, Apple plans to phase out 32-bit Mac apps, just like it did with 32-bit iOS apps. Apple says macOS High Sierra is the last version of macOS that will support 32-bit apps without compromises.
Top Rated Comments
"Fixed an issue that may have resulted in corrupted pictures, Preview opening to solid red
or solid blue, missing controls in QuickTime player, missing icons in the menu bar, or the
failure to highlight items in Microsoft Office."
There are no laws saying how betas should progress. But usually you don’t implement something entirely new between beta versions.
There's just not enough new features to justify breaking so many things and adding spinning beachballs to processes that didn't happen before. If this has to do with the 32 bit apps thing, then I'll jump into that category against that too.
If Microsoft did something like this, Apple would be making commercials ridiculing them. Remember the I'm a Mac commercials ridiculing Microsoft security? Apple is fast becoming what it used to ridicule.
The poster child for this failed testing is the Command-B bug. How can BOLD via Command-B work properly in every word processing program or website like MacRumors, but yet work inconsistently in the MAIL program? This boggles my mind. Others say they do not have this problem, but it's nearly impossible for this bug to be just specific to my Mac Pro.