Jump to content

Recommended Posts

Posted

Yesterday I upgraded my trial version of Affinity Publisher 2 to the paid version. It proceeded to update the software and I thought all good to go. However, when I went to open a file created by a friend in the exact same software I received this error message, as can be see in the photo.

Failed to open document - This file includes features from a later version of Affinity.

As I have the latest updates surely this is impossible? I have tried:

  • restarting the laptop
  • reinstalling the app
  • restarting the laptop again
  • reinstalling the app again
  • restarting the laptop again
  • Shut down over night

But nothing has worked. I'm still getting the same error message. My friend has also tried saving the file under a different name, but nothing has worked.

I am able to open older files but not newer ones. When I've reinstalled the App is says I have the latest version. So I am not sure what to do. Very frustrating, especially now that I have paid for the App...

WhatsApp Image 2023-09-07 at 10.08.34.jpg

Posted

Are you sure your friend is using the same version as you and not a beta version of the software?

Could you upload the file here?

Acer XC-895 Core i5-10400 Hexa-core 2.90 GHz : 32GB RAM : Intel UHD Graphics 630 – Windows 11 Home - Affinity Publisher, Photo & Designer, v2
(As I am a Windows user, any answers/comments I contribute may not apply to Mac or iPad.)

  • Staff
Posted

Welcome to the forums @Eilidh,

Along with what Paul's mentioned with your friend running the beta, he could have also downloaded the 2.2 update that was unintentionally sent out to the release apps back at the start of August, he can check if this is the case by opening the standard Publisher 2.2 app and going to Help > About (on Windows). If this is the case the below FAQ instructions will need to be followed to rectify this on his device.

If this is the case (or if he is running the beta apps) You'll need to download the separate beta apps in order to open and access his files, I've linked the signup page below.

https://affinity.serif.com/en-gb/affinity-beta-program/

Posted

I am the person who saved the problematic file in Beta, with the 2.2 update of which I knew nothing till just now.  The difficulty I have is how to ensure that the important document will not be irretrievable for both of us if I roll back to before 2.2, as any back-up would surely also have been saved in 2.2.

SPNS Newsletter_Aut 2023_v3.afpub

  • Staff
Posted

Welcome to the forums @Fothad,

1 hour ago, Fothad said:

I am the person who saved the problematic file in Beta, with the 2.2 update of which I knew nothing till just now.  The difficulty I have is how to ensure that the important document will not be irretrievable for both of us if I roll back to before 2.2, as any back-up would surely also have been saved in 2.2.

I would suggest uninstalling your current Publisher app as per the instructions in the linked FAQ below, and then re-installing the correct version again (2.1.1).

You can then sign up and download the beta apps (which install as separate applications to the normal release apps) and then continue to work on your files which have been saved in 2.2. The attached file in question opens without any problems in the 2.2 beta app.

https://affinity.serif.com/en-gb/affinity-beta-program/

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.