File access lost then app closes / crashes

[muddyfrog]

When working on a file at times it gives an error Failed to save document because access to file was lost.  Once that happens the app just closes without saving the changes.  This never happened in version 1.

 

[Ron P.]

Hi @muddyfrog,

Is the file(s) located on a Network drive, external drive or local drive? This does happen with files stored on external media. Just a momentary connection loss will cause this area. Serif recommends when working on files, have them on a local drive.

[muddyfrog]

It is on a network drive.  It is on a small gigabit network with SSD drives.  The files are shared between workstations so a local copy is not useful for our workflow.  This worked flawlessly with V1.

 

If there is no hope for this to be looked at, how can I rollback to version 1?  The files are different format and cannot find a way to convert back to v1.

Edited November 18, 2022 by muddyfrog

[NathanC]

Hi @muddyfrog,

We do have an issue logged with the developers which relates to this error message appearing when the file's access to the NAS drive has been lost (even if it is later restored) during an editing session which prevents further saves. I've added your report for consideration.

V2 files are not backwards compatible with V1, so any native affinity files saved in V2 will not open in V1.

[ronditlesauvage]

Having the same problem - the file is on Google Drive, though it should be working with a local copy...

Very annoying problem, thought the recovery file is usually pretty much up to date.

[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.