Files Opening As Read Only Since updating to V2.2.0.

[Dee A]

Since I have updated Affinity Publisher and Designer to version 2.2.0, my files switch from editable to Read-Only as I work on them. It is becoming frustrating as I am constantly having to create new Save As files. Is anyone else having this issue with the update? Does anyone have any insight to how to fix it?

There are two errors I am getting. The first: "Failed to save document: File Name. Internal error: The file was opened as Read Only. You should only be able to do a Save-As.

The second error is: Failed to save document: File Name. Save failed because access to the file was lost. Do you wish to save the document to a new file?" with "Save As..." and "Cancel" as options.

I am running the apps on Win 11.

My Affinity Photo app works fine, which I think has to do with I have avoided updating it to the newest version.

And I have seen this was a problem previously:

[walt.farrell]

The most recent report of this that I've seen was due to the Windows Controlled Access Setting in Defender, though other anti-malware (anti-ransomware) products could also cause problems like that. So you might check that.

Also, while you have the file Open, please show us a File Explorer screenshot showing that file and the files around it alphabetically. In addition to the file you're working on you should have another file with the same name but ending in ~lock~

[Dee A]

@walt.farrell,

Thank you for the response.

As requested, here is the screenshot of my File Explorer featuring the multiple files. You will see that is there no secondary file ending in ~lock~ .

When first opened, I was able to work on it for about six minutes before I got the Save As message again. This is the screen shot showing File Explorer from within Affinity Designer. Since then, I have created a new folder on my One Drive, adding a new Save As file in there (instead if where it was in my iCloud). The new file has been saving just fine since.

It could just be good old cross-platform discontent. I will consider this a win. Thank your for helping me look/think in a different direction to solve this!

 

[walt.farrell]

1 minute ago, Dee A said:

You will see that is there no secondary file ending in ~lock~ .

But it's not a listing from File Explorer itself. It's a listing from the Affinity application doing an Open, which is a filtered list of files.

It needs to be a listing from the File Explorer application directly.

[PaulEC]

1 hour ago, walt.farrell said:

In addition to the file you're working on you should have another file with the same name but ending in ~lock~

Don’t you need “Show hidden files” to be enabled in order to see these files?

[walt.farrell]

22 minutes ago, PaulEC said:

Don’t you need “Show hidden files” to be enabled in order to see these files?

Perhaps. I always have it set that way. Thanks for mentioning it.

[Dee A]

Honest - moving the file from my iCloud drive to my local drive has magically fixed it. I think what might have been happening is a disconnect in syncing files. I have been able to work in one file for the past hour, saving often, without any issue.

Thank you, Walt, for helping me rethink the way I was troubleshooting. For the record, my File Explorer showed the same thing as opening via the App. As per PaulEC, I will also change the setting to show hidden files as well for future troubleshooting.

[NathanC]

Welcome to the forums @Dee A,

This issue has also been reported by a different user using the Windows iCloud drive, I've replicated the issue and it has been logged with the developers.