Unable to change .afphoto file name

[Cpoole]

So I recently updated to 1.8... (very late I know) and have been having serious trouble when saving my documents.

Steps to recreate:

• Opened any image in affinity designer

• Make any change to the photo

• Save as and change the name but leave the .afphoto un changed

• Produces error message attached

• When reopening the file, I get another error message saying "The file type is not supported"

I do not get this error when the file name is not changed. This is not ideal though as I end up with lots of files with stupid names such as DSC02780, and if I try rename this file I am unable to open it and I get the same error of "The file type is not supported".

Hopefully I can get some help here as I do love affinity photo but this is a very bad bug that has made me lose a lot of my work.

[v_kyr]

So you mean renaming or resaving under a different name via the apps "Save As..." panel here doesn't work?

Beside that, your shown Info box panel contains an app bug too, the two "\n\n" newline characters aren't handled correctly and are instead printed together as parts of the output strings. - You can file in an UI bug report under bugs APh Win for that info panel.

[markw]

At step 3 above, on Mac you have to actually change the extension to .afphoto by typing it in. After doing this you get a warning message.
If you choose Use Both, before opening the new file you can change the extension to just .afphoto again and it will open in APhoto correctly.
I wonder why you were not given that first warning message?

[John Rostron]

I think that you need to clarify: are you using Affinity Photo or Affinity Designer?

4 hours ago, Cpoole said:

• Opened any image in affinity designer
• Save as and change the name but leave the .afphoto unchanged

John

[Old Bruce]

4 hours ago, Cpoole said:

Steps to recreate:

• Opened any image in affinity designer
• Make any change to the photo
• Save as and change the name but leave the .afphoto un changed
• Produces error message attached
• When reopening the file, I get another error message saying "The file type is not supported"

If you are in Designer and you are doing File > Save As... you are saving a Designer file, the file extension will be .afdesign. I guess that Designer cannot save .afphoto files in that it cannot save as any other file format e.g.. PDF. 

Note that if you want to you can still open it in Photo even though it has the .afdesign extension.

[walt.farrell]

1 hour ago, Old Bruce said:

If you are in Designer and you are doing File > Save As... you are saving a Designer file, the file extension will be .afdesign. I guess that Designer cannot save .afphoto files

The file formats of .afdesign, .afphoto, .afpub, and .aftemplate files are identical; only the extensions are different.

And (at least on Windows) it is easy to use Save As with Designer and save a .afphoto file; you just need to provide the complete file name and extension. I don't have a Mac to check how easy it is there.

[markw]

34 minutes ago, walt.farrell said:

The file formats of .afdesign, .afphoto, .afpub, and .aftemplate files are identical; only the extensions are different.

And (at least on Windows) it is easy to use Save As with Designer and save a .afphoto file; you just need to provide the complete file name and extension. I don't have a Mac to check how easy it is there.

See my post above for what happens on Macs.

An yes in practice all the files internally are the same regardless of extension but each app insists on using it's own specific one.

[RNKLN]

32 minutes ago, walt.farrell said:

I don't have a Mac to check how easy it is there.

Very easy. You indeed have to explicitly add the .afphoto extension, else it will assume .afdesign. And you do get the warning message (if you want to replace it or keep both extensions), in case you use .afphoto.

[walt.farrell]

22 minutes ago, markw said:

but each app insists on using it's own specific one.

That's appropriate behavior, because the extension will determine the default application that will open the file.

[Cpoole]

I am very sorry, i just miss typed in my original message, I am using affinity photo. So sorry

[Cpoole]

On 5/10/2020 at 10:55 AM, Cpoole said:

So I recently updated to 1.8... (very late I know) and have been having serious trouble when saving my documents.

 

Steps to recreate:

 

• Opened any image in affinity designer

   

• Make any change to the photo

   

• Save as and change the name but leave the .afphoto un changed

   

• Produces error message attached

   

• When reopening the file, I get another error message saying "The file type is not supported"

   

I do not get this error when the file name is not changed. This is not ideal though as I end up with lots of files with stupid names such as DSC02780, and if I try rename this file I am unable to open it and I get the same error of "The file type is not supported".

 

Hopefully I can get some help here as I do love affinity photo but this is a very bad bug that has made me lose a lot of my work.

 

• Opened any image in affinity Photo

   

• Make any change to the photo

   

• Save as and change the name but leave the .afphoto un changed

   

• Produces error message attached

   

• When reopening the file, I get another error message saying "The file type is not supported"

Very sorry that is what its ment to say.

[markw]

Hello again,
With your new recipe I am totally unable to reproduce your problem or generate any form of warning message.
I’m on macOS Mojave but not really sure that’s significant?
On my Mac after clicking Save As…, the save window that opens never shows the .afphoto extension in the title field. And I can’t recall it ever doing so in the past.
After saving, the file extension is automatically added to the end of the file name.
Any chance you could post a recording of your process and what happens to you?

[Cpoole]

6 hours ago, markw said:

Hello again,
With your new recipe I am totally unable to reproduce your problem or generate any form of warning message.
I’m on macOS Mojave but not really sure that’s significant?
On my Mac after clicking Save As…, the save window that opens never shows the .afphoto extension in the title field. And I can’t recall it ever doing so in the past.
After saving, the file extension is automatically added to the end of the file name.
Any chance you could post a recording of your process and what happens to you?

Im sorry about the qualty, I am only able to use my phone as OBS dosent want to work with af photo. The first error message is just asking if i want to replace another file called test. the main error still appens with or without replacing the file. Hope this helps. Also I tryed saving as .afdesigner on af photo and that works fine even when changing the name

[v_kyr]

IMO you don't have to type in the extension (.afphoto) under "Save As...", that should normally be added automatically by Affinity Photo itself when saving into the file system.

[Cpoole]

1 minute ago, v_kyr said:

IMO you don't have to type in the extension (.afphoto) under "Save As...", that should normally be added automatically by Affinity Photo itself when saving into the file system.

I know this, but someone told me that could be a fix earlier

[v_kyr]

What did the first Warning panel tell, the one with the yellow warn icon?. -  That was unreadable for that bad quality video, maybe you should try Monosnap or ScreenToGif or the like for screenrecording on Windows.

[Cpoole]

9 hours ago, v_kyr said:

What did the first Warning panel tell, the one with the yellow warn icon?. -  That was unreadable for that bad quality video, maybe you should try Monosnap or ScreenToGif or the like for screenrecording on Windows.

I will give that a go. It was saying if i want to replace another document called test. the error happens even if i use a new file name that isnt already taken

[Cpoole]

This is an updated video of the error (better quality), hope it helps

[v_kyr]

Yes that video is better!

AFAI can see you are operating (saving/loading and accessing) that file from a remote OneDrive connection and during those processes the Affinity app has problems to operate and reload from the mounted OneDrive. - It might be safer to do such image manipulation tasks on the local filesystem (your local hard disk) instead, in order to not get errors. Afterwards exchange images via copying them back over to OneDrive.