Jump to content
You must now use your email address to sign in [click for more info] ×

Failed to save document


Recommended Posts

I decided to try real work in the beta and after an hour or so I got a save failure. I don't know if it's beta related or not but I haven't had a save failure in ages. I'd done nothing interesting since my last incremental save except for editing text and copying and pasting one inline image. I was saving to iCloud (which I always do) but saving to a local drive didn't make a difference, it just created a 0 byte file.

Hopefully it's a one off but I'm mentioning it in case it's not an isolated incident.

Screenshot2024-04-19at1_56_28PM.png.9324004ee2a7254f473d32b8e948b471.png

EDIT: I should add for others that doing real work in a beta is at our own risk. I choose to accept the risk so I can give it a good workout but I save and back up frequently in case I run into an issue like this.

Edited by MikeTO
Link to comment
Share on other sites

I had this save failure again just now. I'm updating the screenshots for the updated panels in my manual. All I'd done since the last save was overwrite an inline image (grouped) which updated automatically, double-clicked the group and moved a couple of the callouts and callout lines. Deselected the group and saved.

Again I couldn't save the file to a local drive and had to close it. I restarted Publisher for good measure but that may have been unnecessary.

I hadn't had any save failures in 2.4 or 2.3, and probably not since the early 2.0 versions, so there's something going on with the beta. I wonder if it could be related to the recovery prompts. I had been prompted to recover the file when I opened it but declined since I knew I'd saved and closed it properly.

Link to comment
Share on other sites

It happened again just now. The only thing I'd done since opening the file (my Publisher manual) was delete many small paragraphs (I'm editing a long list in an appendix). I didn't do anything with any images or linked resources.

I tried closing and re-opening the document to save it under another name but that failed, I had to restart Publisher.

Link to comment
Share on other sites

And again just now. This time I was copying and pasting text from the end of paragraphs to the start of paragraphs, for a dozen paragraphs in a row - they're fake tables made up of tabbed text and I was changing the order of the "columns". No images involved.

I wish the recovery prompt issue would strike when this happens but it never has. Fortunately, I save so often that I can just copy what I've edited to a new document, save it, and restart Publisher to retrieve it.

Link to comment
Share on other sites

I've gotten this error as well

2021 16” Macbook Pro w/ M1 Max 10c cpu /24c gpu, 32 GB RAM, 1TB SSD, Sonoma 14.4.1

2018 11" iPad Pro w/ A12X cpu/gpu, 256 GB, iPadOS 17

Link to comment
Share on other sites

not sure if this is the same error but seems related. trying to open file from last beta into current beta... i can upload file via private dropbox link...

 

image.png.5a8e757540405f17513398f81337e948.png

2021 16” Macbook Pro w/ M1 Max 10c cpu /24c gpu, 32 GB RAM, 1TB SSD, Sonoma 14.4.1

2018 11" iPad Pro w/ A12X cpu/gpu, 256 GB, iPadOS 17

Link to comment
Share on other sites

A clue. Most of the time when I get the recovery version prompt (https://forum.affinity.serif.com/index.php?/topic/202721-recovery-version-prompt/) it's for a throwaway test document and I ignore it, but I also get it a lot with my real documents. I've been paying more attention and for all of the save failures I had yesterday and today, and there were enough to form a pattern, they were preceded by the recovery version prompt. Perhaps these two issues have the same root cause?

Link to comment
Share on other sites

  • 2 weeks later...

I know not many people are reporting this but they may not be doing real work in the beta. I experience a save failure with the 2.5 beta and lose work several times a day, something I hadn't really experienced in the past year. I haven't been able to find a repeatable series of steps to trigger it.

Link to comment
Share on other sites

It's definitely happened to me several times as well... 

2021 16” Macbook Pro w/ M1 Max 10c cpu /24c gpu, 32 GB RAM, 1TB SSD, Sonoma 14.4.1

2018 11" iPad Pro w/ A12X cpu/gpu, 256 GB, iPadOS 17

Link to comment
Share on other sites

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.