#Checkbook pro support mac os
#Checkbook pro support update

#Checkbook pro support update

Update : This issue also affects QuickTime Player on macOS 11.5 and later.

Tumult Hype 4.1.7 (save/move) Fixed in macOS 11.6.

Pixelmator Pro 2.1.3 (new/save/move/export) Fixed in macOS 11.6.

Pixelmator 3.9.8 (export – except for PDF) Fixed in macOS 11.6.

OmniGraffle 6.6.2 (move) Fixed in macOS 11.6.

OmniOutliner 5.8.5 (move) Fixed in macOS 11.6.

Apple TextEdit 1.16 (save to existing file) Sorta fixed in macOS 11.6 (temporary files aren’t removed, document may save but eventually can’t be because it’s “locked”).

Apple QuickTime Player 10.5 (move) Fixed in macOS 11.6.

Apple Preview 11.0 (move) Fixed in macOS 11.6.

Apple Photos 6.0 (export unmodified originals) Fixed in macOS 11.6.

Apple Contacts 13.0 (export contacts archive) Fixed in macOS 11.6.

Apple Configurator 2.14 (move) Fixed in macOS 11.6.

Apple Calendar 11.0 (export calendar archive) Fixed in macOS 11.6.

Apple Books 3.2 (drag audiobook to volume) Fixed in macOS 11.6.

CheckBook Pro 2.6.20 and earlier (save/backup/move) – Update to 2.6.21 now Fixed in macOS 11.6.

CheckBook 2.6.20 and earlier (save/backup/move) – Update to 2.6.21 now Fixed in macOS 11.6.

Audiobook Builder 2.1.4 (new/save) – Workaround coming in 2.1.5 Fixed in macOS 11.6.

The applications (and known actions) affected by this issue are now: We value everyone’s data and time that much.

In the near future, all our applications will warn you when you try to use other formats or flavors of SMB until you tell us not to.

#Checkbook pro support mac os

So our faith in Apple’s support for anything besides APFS or Mac OS Extended, or SMB to those on recent macOS hosts, got taken to the woodshed, you might say, and we just won’t rely on them anymore. If we caused an issue like this, then handled it as Apple has, we wouldn’t be able to live with ourselves – and we’d be out of the Splasm business, to boot. No one from Apple ever communicated with us about our bug reports – and there’s no sign any engineer even read them. There’s no mention of it in the macOS 11.6 release notes. In the 1.75 months since we told Apple about it, something close to a hundred of our users – that we know of – lost data and needed help restoring a backup while we spent an insane amount of time we didn’t have (and our families didn’t want to give us) testing and coding around the issue. However this thing slipped through the cracks, it took Apple 7.5 weeks to move on it with two minor macOS updates in the meantime. Copying files to or saving files on FAT, ExFAT, and SMB volumes is not uncommon, especially since almost every external drive comes pre-formatted for Windows. Thank you all for hanging in there!Įven though Apple seems to have resolved the issue and we’re breathing easier over here, we want to leave a note for the record: The vast majority of Apple developers have used NSFileManager or copyfile(). We’re testing each application in the list below to be sure, but our own applications, Apple Preview, and Tumult Hype all appear to be working as designed, so we think we’re out of the woods. Update : Great news! macOS 11.6, released earlier today, seems to have addressed the fundamental issue with FAT, ExFAT, and some SMB volumes. This issue affects a small number of our users, but we need you to read through just to be sure you’re not in that group.