Can't (re)open .afpub file after reinstalling win 11

[gaiaswind]

Hi dear affinity Team,

I would like to report a bug regarding publisher V2. After my computer had a problem I had to reinstall Windows 11. After that I am not able to open my file that was perfectly fine before. See the screenshot for more information.

 

The file was created in V2 - so it's not a V1 to V2 problem.

I tried using the app via windows store and the "normal" installation.

 

Best regards

[carl123]

Can you upload the file to the forum or is it private?

[gaiaswind]

29 minutes ago, carl123 said:

Can you upload the file to the forum or is it private?

I'm sorry, I can't upload it to the forum due to the content.

 

I just opened a different file from the same creation time, which opened perfectly fine - so it's even more weird 🤨

[carl123]

Please ensure you are using V2 to open the file

If you are opening it in File Manager by double clicking etc the file association may still be pointing to V1 and it's V1 that is trying to open it

Other than that, without the file, I have no idea

Maybe, someone else will

[gaiaswind]

1 hour ago, carl123 said:

Please ensure you are using V2 to open the file

If you are opening it in File Manager by double clicking etc the file association may still be pointing to V1 and it's V1 that is trying to open it

Other than that, without the file, I have no idea

Maybe, someone else will

I  am opening it via V2, so that as well is not the problem.  

edit: it's a rather big problem for me, as I have to continue working on the file, so I hope a solution can be found soon 🙂

[carl123]

Hi 

This error message has been cropping up a lot lately

"The file includes features from a later version of Affinity"

I have not, as yet, seen a way to open any file that gives that error message

Serif are aware and will hopefully fix it in a later patch/update

If you need it fixed sooner all you can do is request a private dropbox link (in this thread) and one of the support staff will supply one.

(Note: They may be able to fix this problem for you now or they may still be working on the problem - I don't know)

 

[NathanC]

Hi @gaiaswind,

This error message appearing on files created in V2 is an issue currently logged with the developers for resolution. I've bumped the issue with your report.