move-on-by 4 hours ago

> “As a developer of macOS security tools, it’s incredibly frustrating to time and time again have to deal with (understandably) upset users (understandably) blaming your tools for breaking their Macs, when in reality it was Apple’s fault all along,”

I would like to understand this better. Were there not any beta releases that these companies could have tested with in advance? Or were changes made between the beta and the release that broke things? Or something else?

  • sephamorr an hour ago

    Per Patrick Wardle, this was well reported to Apple during beta.

    https://x.com/patrickwardle/status/1836862900654461270

    • move-on-by 11 minutes ago

      Thank you, this makes the frustration in the above quote more understandable. For anyone wanting to avoid the x click:

      > Worth stressing this was reported to Apple before the GA was released (by multiple people, to multiple teams/orgs within Apple) so Apple 100% knew about this, and shipped macOS 15 anyways

  • Spivak 3 hours ago

    This is the part I'm missing too. Major versions are the time to ship braking changes, did none of these companies bother to test their software that mucks deep in the plumbing of the OS?

    • 1over137 3 hours ago

      It is very typical to file bugs against even the first beta and not see them fixed before GM, or even ever.

    • RockRobotRock 3 hours ago

      Is there even an equivalent to WSUS on macOS that lets admins block an update until it's tested?

      • salmo 3 hours ago

        Yeah. There’s Jamf and similar tools. Companies often block major updates until their 100 agents all officially support it. Oh, and do cool things like not letting you change your background or whatever random settings some admin decides are good.

yawnbox 4 hours ago

all my wireguard tunnels could not connect upon upgrade. disabling the macos firewall allowed me to use my tunnels again, fyi.