Error while saving on USB drive - Save failed because access to the file was lost.

[becike]

Hi,

I use Affinity Photo 2 2.0.0, Mac M1 with Ventura 13.0.1 (22A400)

I have a 1TB Seagate Ironwolf HDD connected over USB to my Mac.

In the last weekend I upgraded my MacOS from Monterey to Ventura.

After that, when I try to save a project file to the external 1TB HDD, I get various error messages: Save failed because access to the file was lost. or Access to the document's file was lost. The file is required at all times.

I tried the save different project files in Affinty Photo V1 and in V2, too. Before the OS upgrade everything worked fine.

I tried to catch the issue with the Mac's Console log, I attached the log, too, perhaps it can help to solve the issue.

[Chris B]

Hey becike,

This is logged so I'll attach your feedback to the report.

[Slaphappy]

I am having this exact same issue and it's been driving me bonkers... have you found a solution to this yet, becike?

My working files are on an external drive connected via USB-C. This was happening at the tail end of Monterey for me, and it's carried over to Ventura. It was happening with Affinity Photo 1, and I just paid to upgrade to Photo 2, and it's happening there too. Same error as your screenshot.

Note: Saving as a different file works, whether that "different file" is a new one or an existing one (that isn't the one I have open). So I've had to get into the habit of having two copies of the same working file. And when I want to save, I "save as" #2. Then if I want to save again, I save as #1. 

I've lost so much time to this error, because it just instantly shuts everything down, instead of leaving the document open for me to try again in a different way... just gone. And I have to go back to wherever the recovery file puts me.

Anything I can attach beyond what becike has to help fix this?

[Ottie]

I have exact the same issue! (MAC M1, Ventura, external drive 1TB connected via USB-C, same error-message).

I can open an afphoto-file stored on the USB-C drive, but I can´t store the file after doing a modification to the photo. Instead, I get the error-message mentioned above.

 

[walt.farrell]

@Slaphappy, @Ottie: Welcome to the Serif Affinity forums.

It's probably this known issue with Affinity and Ventura: 

Serif haven't said when there will be a fix, but I expect they're working on one.

[Affinity Info Bot]

The issue "Files saved to removable storage/network drives can lose access force close" (REF: AFB-5409) has been fixed by the developers in internal build "2.2.0.1900".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.

[filippoguidarelli]

Hi, I got the same error message but the strange thing is that I'm working on my dektop and I don't have any resource in any storage device. Btw, saving is actually working even if the system says it's impossible/failed. 

[MikeTO]

27 minutes ago, filippoguidarelli said:

Hi, I got the same error message but the strange thing is that I'm working on my dektop and I don't have any resource in any storage device. Btw, saving is actually working even if the system says it's impossible/failed. 

If you're saving to your desktop on macOS and haven't changed your system settings, you are saving to iCloud because that's where the desktop folder is stored. Affinity used to have a lot of issues with iCloud.

Which version of Affinity are you using?

[filippoguidarelli]

36 minutes ago, MikeTO said:

If you're saving to your desktop on macOS and haven't changed your system settings, you are saving to iCloud because that's where the desktop folder is stored. Affinity used to have a lot of issues with iCloud.

Which version of Affinity are you using?

Thanks for the suggestion, but I did not change the settings. I solved it giving publisher complete access to everything, because I have to deliver a job asap and I ahve no time to investigate. But this is the second time I experience annoying/risky issues on the job: working with this suite is becoming quite frustrating

[MikeTO]

17 minutes ago, filippoguidarelli said:

Thanks for the suggestion, but I did not change the settings. I solved it giving publisher complete access to everything, because I have to deliver a job asap and I ahve no time to investigate. But this is the second time I experience annoying/risky issues on the job: working with this suite is becoming quite frustrating

If you did not change the settings you are saving to iCloud. Giving the app complete access won't change a network issue - the network issues are just intermittent.

I use iCloud, too, but I haven't experienced issues since the upgrade to 2.2.1 which addressed most of these intermittent iCloud issues. Can you confirm you're using 2.2.1 or a 2.3 beta?

[filippoguidarelli]

Thanks, I'm using 2.2.1