Affinity Publisher 2 for Windows - (2.4.0 & 2.4.1)

[Patrick Connor]

We are pleased to announce an update for the Windows release of Affinity Publisher 2, version 2.4.0

This build is available as a (sandboxed) MSIX application installer and as an (unsandboxed) MSI/EXE traditional installer.
Please see this FAQ thread for instructions on how to access the unsandboxed MSI/EXE version.

The changes in Affinity Publisher 2 for Windows 2.4.0 are listed in this FAQ forum post:

Those are the changes made since the last release Affinity Publisher 2 for Windows 2.3.1

A subsequent release 2.4.1 is announced here

To get notified when any new releases are made please follow the latest releases thread by clicking here

UPDATING TO THIS VERSION (free for existing customers)

The software version can be seen on the splash screen and the About dialog (in Help > About Affinity Publisher ). 

If you’ve purchased from the Affinity Store — each time you start the Affinity Store software it will check for updates and offer any available update. The Windows builds only automatically checks once per day. In the Help menu there is a manual "Check for Updates". The latest update will install over the top of any earlier version, with no need to uninstall. You can download the latest installer by logging into the affinity store here and find the order in your account and use the "Download" button in there. Alternatively, this new release (and previous versions of Affinity Publisher for Windows) can be downloaded from this link (those installers are NOT for customers who made Microsoft Store purchases).

If you've purchased from the Microsoft Store — Microsoft Store updates are done automatically by the operating system (each time you start the application). If this does not happen for you, open the Windows Store app and click the three dots in the top right corner of the app and then go to Downloads and Updates. Click Get Updates. This should hopefully force the update to show. 

[Patrick Connor]

All Readers

This thread is solely for commenting on this announcement.

Please do not post bugs or problems that you find when using this version of the software in this thread, instead make a new thread in the V2 Bugs on Windows section and questions about usage go in the Desktop Questions forum.

[walt.farrell]

The EXE/MSI version of Designer 2.3.1, and of Photo 2.3.1, both detected the 2.4.0 update and offered to download it.

However, the EXE/MSI version of Publisher 2.3.1 still seems to think it's the latest available:

 

[Patrick Connor]

20 minutes ago, walt.farrell said:

However, the EXE/MSI version of Publisher 2.3.1 still seems to think it's the latest available:

It is likely a caching issue. Please close the application and delete this file and then try again

C:\ProgramData\Affinity\Publisher\2.0\update-unpackaged.json

Indeed you can likely delete all the files in there. Some are historical.

[walt.farrell]

Thanks, @Patrick Connor, but that does not resolve it.

After closing Publisher 2.3.1,  deleting the files, and restarting Publisher 2.3.1, it still did not automatically detect the update, and a manual check via Help > Check for Updates still fails to find it.

 

[Patrick Connor]

Will give it some thought Walt. I do not think this is generically broken

[Duskstalker]

for me all .exe installed applications recognized theres an update and offered me to download it. i installed the .exe applications after uninstalling the msix version at version 2.31 a few weeks ago.

[Affinityconfusesme]

HI @Patrick Connor I had the same issue as @walt.farrell. Since I am using EXE I just downloaded 2.4 from the website, and installed them that way.

[walt.farrell]

5 hours ago, Patrick Connor said:

Will give it some thought Walt. I do not think this is generically broken

Turns out it seems to have been a Firewall issue, Patrick. 

It's odd, because the Firewall was already configured to allow all communications to/from publisher.exe, and it showed the correct install directory (exactly as it did for Photo and Designer). 

I clicked on Allow again in the Firewall configuration dialog, and after that the update check worked