Jump to content

Recommended Posts

Posted

Affinity Version 2.0.4
Mac OSX 10.15.7 (Catalina)
Have tried with hardware acceleration  both on and off.

1) Yesterday using Version 2.0.0 (previous version prior to updating) I opened a PDF document (k-p4.pdf), saved it as an afphoto (k-p4.afphoto) document after modifying.

2) Today I went to open k-p4.afphoto and got this error message: "k-p4.afphoto" was created in Affinity 1. Editing it will make it unusable in the older version. Use "Save AS" to preserve the original file."

3) Clicking OK brought up this error message: "Failed to open file  /Users/MB/Documents/Biz/Brighthouse/k-p4.afphoto  The file type is not supported."

Actually, it appears to be two bugs:

1) Saving a document in Affinity Photos Version 2.0.0 created a version 1 document. (May have been fixed in 2.0.4, but in any case . . . )

2) Apparently Affinity Photos Version 2.0.4 is unable to open a version 1 document.

1.jpg

2.jpg

Posted

Or, the document is corrupted, which could cause both of those errors.

Is it a document you can share publicly? If so, please attach the .afphoto file here so some of us can try it and see if we get the same results.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 18.3.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

Posted

 

2 hours ago, walt.farrell said:

Is it a document you can share publicly? 

Unfortunately it's the signature page on a financial document already with signature so I can't share.

I had a copy of the previous version on a backup so tried to recreate the situation: opened a pdf, and saved as .afphoto

It then opened in version 2.0.4 just fine.

Most likely a corrupted file, then, though unclear how it got corrupted.

 

Posted

Hi @mbabco,

Thanks for your report and we're sorry to hear you're having trouble here!

I'm glad to hear you haven't been able to replicate this issue in a new document, as we're not aware of any underlying issues with creating documents in 2.0.0 for opening in 2.0.4, though this does point to a potentially corrupted .afphoto file as Walt has mentioned.

I appreciate you may not want to share this publicly, but if you wish I can provide a private upload link for the document, such that I can investigate it further.
If I'm still unable to find the cause of this corruption the file can then be logged with our developers for in-depth testing.
This may allow us to determine the cause of this issue and hopefully stop it from occurring in future versions, though due to the nature of corrupted documents we unfortunately cannot offer any guarantees.

If you are able/willing to provide this document privately please do let me know :)

Posted

I certainly understand, thanks for letting me know - hopefully this issue does not occur again for you but we're here to help if you have any further questions :)

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.