The most recent replace for macOS Sonoma has one more bug, this time inflicting havoc for customers’ saved information in iCloud Drive.
Usually, if you save information inside your iCloud Drive all of the completely different variations of that file might be saved for future reference. So, in case you’ve been engaged on an enormous mission or task, you’ll be able to look by means of all of the variations of your file if you’ll want to.
That is the case even if you take away a file from the drive; the previous variations of it should nonetheless be out there to you if and if you want them. Sadly for some customers, this new bug erases all of the earlier saved variations when a file is faraway from the iCloud Drive – which might imply all of your work is gone.
Howard Oakley from The Eclectic Light Company said in a publish that customers of macOS 14.4 who’ve enabled the ‘Optimize Mac Storage’ setting must be warned that there’s a danger of shedding all their saved variations of a file in the event that they select to delete or transfer it from the iCloud Drive. Oakley notes that this problem “definitely doesn’t occur in Ventura” and that when examined within the earlier 14.3 updates didn’t observe the issue both.
Clutching my saved information
In case you’re frightened about your individual saved information, don’t! You’ll be able to try to curb the potential menace by both merely not updating your operating system to macOS 14.4 in case you haven’t already, or disabling the ‘Optimise Mac Storage’ setting. This manner, your information received’t be booted off iCloud Drive and neither will any earlier saved variations.
This bug is merely the newest drawback to plague the macOS Sonoma 14.4 replace, following reviews that the replace was breaking some users’ USB hubs and even taking down printers as effectively. So, you’ll need to be as cautious as doable in case you’ve already up to date to the newest model of Sonoma.
To this point there haven’t been quite a few reviews of the bug going round, which suggests it’s seemingly not a widespread problem simply but. We’ve but to listen to any phrase from Apple relating to these bugs, which might be interpreted as excellent news in itself – if Apple hasn’t mentioned something but, that’s a great signal that this can be a minor problem that can most likely be shortly and quietly resolved in an extra replace.
Discussion about this post