Affinity Designer destroying document during save. 'file could not be verified'

[dock]

Twice in the last few months I have pressed Ctrl S only for Affinity Designer to nuke my work.

I would save my work and Affinity has given an error before shutting down completely. It is by far the worst time to ditch someone's work, and makes me wonder whether I should be screenshotting (!) my work before saving, just in case.

I was told via Twitter that this has something to do with using external drives. I'm actually saving to Pcloud, which is a cached local drive. I've never seen another application act like this.

I encountered this first in September, and again one week ago.

[carl123]

You are not alone

https://forum.affinity.serif.com/index.php?/topic/54177-save-failed-because-ownership-of-the-file-could-not-be-verified/

 

[All Media Lab]

Hi,

I noticed this behavior with the use of a USB memory stick and reported the issue in the bugs report panel that appeared.

Never had this problem with the use of a harddrive in my laptop.

This was in Affinity Designer.

Regards,

David 

[dock]

The fact that this bug has been reported for more than a year with no budge makes me worry even more.  

The problem is less about the drive but the fact that Affinity closes/kills the document!! It makes no sense. If a disk is full will it kill my document? If my disk access is slow will Affinity time out and delete my work? The idea that the software is happy to destroy work done is absurd. 

I appreciate that cloud services might make saving non-trivial, but it really should be reasonable that I can choose save without losing my work.