Affinity Designer v2 / Publisher v2 / problems with both.

[Elderly User]

Running v2.0.4 versions of all the above (installed from the Affinity website from my Account) on my iMac Apple M1 chip with macOS Ventura 12.2.1.  

1.  Affinity Designer starts and immediately generates a problem connection window referring to my local NAS server (Check the server name or IP address, and then try again. If you continue to have problems, contact your system administrator).  When this message is OK'd the same message box repeatedly appears and I have to force quit AD.  Have tried removing and reinstalling to no avail.  Same problem occurs when trying to open AD directly by opening a saved document from Finder.

2.  Affinity Publisher - when trying to print document programme immediately crashes.  Can reopen same document.  Tried to export document as a PDF - get the Affinity Publisher 2 quit unexpectedly problem report message box to send problem to Apple.

No problems of this nature with previous versions.  Help for remedies please.

 

[Lee D]

Can you please try the following to see if it resolves your issue as we have this logged with our developers.

Run Terminal and paste this code:

rm ~/Library/Application Support/Affinity Designer 2/mru.dat

What does the document you're trying to print consist of?

[Elderly User]

Hello Lee,

Result for the code above copied and pasted into Terminal attached.  The document in Publisher is an A4 sized document with 13 single pages and a Master page with a table.  Images are embedded.

[Elderly User]

Just tried Publisher and Designer in Beta mode with copy of the same document and still crashed on print command and will not export as PDF. 

[Affinity Info Bot]

The issue "App attempts to reconnect to disconnected SMB share on launch" (REF: AFB-7024) has been fixed by the developers in internal build "2.1.0.1728".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.

[Elderly User]

Excellent news, thanks for the info. and will do.