darmabum

I think we agree, but I'm still going to nitpick a little. Serif claims iCloud (and Dropbox) compatibility, and while there very likely is a clear warning somewhere in the manual, it's nowhere near obvious enough for such a (literally) potentially unrecoverable catastrophic failure that has been reported for several years. There's a difference between losing a few hours of work because I wasn't saving, and suddenly losing the entire project, from the beginning, including snapshots. I can imagine several options that Serif might offer, such as backups to a separate location, timed SVG exports, our at least better caching that might rollback to some prior state (Dropbox should be able to do this, and come to think of it, I have Arq). That said, it was *wonderful* that the file could be resurrected from a PDF export.

Thank you! And yes, I saw several mentions of this online from 2019 onward, and the recommendation of saving locally is understandable, but somewhat defeats the convenience of multi-device edits. So, to be clear, "locally" means not iCloud (even tho its supported), Desktop and Documents folder if they're also sync'd (which was my problem), and maybe not Dropbox either. I fully understand that all of these services can be unreliable, but maybe some kind of temp auto saved state for just these kind of events should be considered.

Just FYI, I was able to open the exported PDF in AD, and it *looks* like all the layers and content are still there and editable. So far so good. Original Affinity file is 404.

Working in AD2 and AP2 on MacOS for the past week on vector document, saved in icloud, and saved a snapshot yesterday. Finally finished today, and exported a PDF to the desktop (iCloud). The PDF exported fine, but AD immediately responded that the original file could not be verified and had to be closed (no options, just terminated). Now, attempts to open the file in AD or AP reports that the file is corrupted. Did I just lose a week of work?