Here's a novel one

[dmstraker]

"Save failed because ownership of the file could not be verified."

Plus the delightful "The document must now be closed" (with no chance of saving). Boom.

Fortunately when I reopened it, it recovered where I was. Got me going for a moment there, chaps.

 

[MikeTO]

Hi Dave, Serif will likely want to know where was the document was last saved. On your internal drive, an external drive, a network drive, or a cloud? If a cloud, which one?

I've encountered this error with documents on iCloud. Serif always recommends to save on the internal drive but I'm living dangerously. 🙂 I've only had this error a few times, typically the version of it I get doesn't force close the document.

Good luck

[Chris B]

It sounds a bit 'networky' so I'm assuming network/cloud unless it's some permissions issue with the user on a local drive?

It's disappointing that it shuts the document down. If it's complaining about permissions/ownership it should just not let you save it rather than close it but I'm not sure if this is some safety measure? I could probably get it looked at.

[PaulEC]

I've had this sort of problem a few times, with various software, and I must agree that the bald "This document must now be closed" type of message is both useless and infuriating, sometimes losing a fair amount of work. (Yes, I know, you should save your work as you go, but we all make mistakes, and it's easy to be wise after the event!)  It would be great if you could just go back and try to sort the problem, but it would be nice to at least have the option of saving the file before it closes!

[NotMyFault]

It's not such novel 😎

Has been reported before, even for V1.

 

https://forum.affinity.serif.com/index.php?/search/&q=Save failed because ownership of the file could not be verified.&quick=1

[JoergWe]

I encountered the same issue using Publisher v2 and also HATE that it closes the file without giving me a chance to save my changes. The auto-save/recover helps to minimize the damage. I had my file in a cloud drive and have now moved it from there to my local drive. I will update this if I get more issues, but I assume that was the problem.

How do we let Affinity know to fix a problem? Closing the file and not saving changes it the problem I feel needs to be fixed for sure.

[DieterW]

This is an issue for all three products and it is extremely annoying. For me it is new with V2, as I did not experience with V1. I solely work form my NAS, i.e. all files (and linked resources) are stored on the NAS from where they are opened.

When I send the PC to sleep and wake up again then this issue arises every single time. Very funny if you work with lot of files open you have to reopen manually after the application was closed without any choice. Good luck with recalling which files you had open so you do not lose the recovery state... After recovering you cannot save the file manually (Save as) over the original as this is still locked and write protected. So you have to save with a different file name, then deleting the old one (not with Windows as it tells you the file is still in use, so you have to directly on the NAS) and then renaming the new file back to the old name. So much joy!!!

First, it should not happen at all. It worked with V1, so I do not see any reason why it cannot work in V2.

Second, how on earth came someone up with the idea to deny me the option of saving the file manually before it is closed? I mean, honestly...

[MikeTO]

6 hours ago, DieterW said:

Second, how on earth came someone up with the idea to deny me the option of saving the file manually before it is closed? I mean, honestly...

When an app does this it means the open document is corrupted in memory and therefore it can't continue to display the document or let you save it. I've experienced this with a document with linked resources on iCloud. It's not good and needs to be fixed but the app is displaying this error only because it has to. When you see this error you should restart the app - if something this bad has happened it would be a good idea to restart.

[DieterW]

No, that is not the case. I can continue to work on the document without issues. So it cannot be corrupted. It is just a saving issue.

[nodeus]

Maybe a good case study for affinity app would be to suggest that the user save the document under a new name or add a postfix to the name, such as _saveproblem...