Jump to content

Recommended Posts

Posted (edited)

hELLLLP. I keep getting this error when trying to saving a Publisher document. I tried saving to other locations (both on Cloud and on desktop). I've been unable to download the latest update of Publisher (I keep getting an error message when I attempt to do so), so not sure if that's part of the problem.

Screen Shot 2025-04-09 at 4.45.02 PM.png

Screen Shot 2025-04-09 at 4.50.44 PM.png

Edited by Heidi715
added a screen shot
Posted

Hi Heidi, this may be happening if Affinity is momentarily losing connection to the file which can happen if your network connection is intermittent.

Serif recommends not saving to iCloud and to instead save to a folder on your internal drive that is not synced to a cloud. Note that your Mac Desktop and Documents folders are synced to iCloud unless you turn that off. It's better to create a folder outside of your Desktop and Documents folders to be safe.

Posted

Windows or Mac, it seems these cloud based systems are giving all people pain in the behind ;)

Windows 11 - 24H2 ⊕ ASUS PRIME X670E-Pro ⊕ AMD Ryzen 9-7900X ⊕ Arctic Liquid Cooler II ⊕ 64GB RAM ⊕ OS SSD Samsung 980Pro 2Tb ⊕ Cache SSD Samsung 870 EVO 1Tb ⊕ Video HD WD Blue 4Tb ⊕ Geforce RTX 3060 12Gb ⊕ BenQ SW270C ⊕ Dell U2412M ⊕ Affinity Photo 2.5.5 ⊕ Affinity Designer 2.5.5 ⊕ Affinity Publisher 2.5.5

Posted
On 4/10/2025 at 4:25 AM, RobWu said:

Windows or Mac, it seems these cloud based systems are giving all people pain in the behind ;)

@RobWu ugh for real. Every other time I attempt to save I get some rando error message.

Posted

Ich habe das im Forum ähnlich beschrieben.
Schaut mal. Alle Ressourcen sind weg.
Ich arbeite lokal auf einer Festplatte und nicht in einer Cloud.
Das Problem hatte ich erstmals mit der aktuellen Version 2.6.2.
Mein System: Windows 11 / 64 Bit

 

Posted

Is it just me, or are these errors popping up more since the latest two updates of Affinity?
Fortunately I haven't really had to deal with this, but I'm always saving in incremental versions, and backing up stuff daily (you know, like you should...)

I also never have seen this in any other software application tbh, even when dealing with massive files over a network.
Maybe the peeps at Affinity should look into this a bit more to see if there's a easy fix?

Windows 11 - 24H2 ⊕ ASUS PRIME X670E-Pro ⊕ AMD Ryzen 9-7900X ⊕ Arctic Liquid Cooler II ⊕ 64GB RAM ⊕ OS SSD Samsung 980Pro 2Tb ⊕ Cache SSD Samsung 870 EVO 1Tb ⊕ Video HD WD Blue 4Tb ⊕ Geforce RTX 3060 12Gb ⊕ BenQ SW270C ⊕ Dell U2412M ⊕ Affinity Photo 2.5.5 ⊕ Affinity Designer 2.5.5 ⊕ Affinity Publisher 2.5.5

Posted

This just happened to me again. Previously, doing a Save as, getting out of APub, rnaming the Saved as file in the filesystem, then getting back into APub was an annoying workaround that actually worked. This time I had just spent an hour on a book document, tediously adding index marks. It not only failed on the Save as reported in this thread, it also failed on the Save as, complaining about lost access to other information needed by this file, and offering to Save as. That second Save as actually worked, but all my index marks were lost in it. So basically an hour of work shot. So in this case, this particular bug is way more than just annoying.

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.