Jump to content
THESE FORUMS ARE READ-ONLY: Please Read Me ×

Recommended Posts

Posted

I had a series of issues with Publisher after the update where saving a file was problematic. I would get an unable to save message then publisher closed. I was ok when opening as the recovery file would open. However last attempt it didn't prompt for recovery. I get a message that the file is open in another app, despite this not being the case (Mac shutdown along with all apps to prove). The backup file states format not supported. This is a disaster as it has 2-3 weeks work on a project. Any help appreciated. 

Publisher 2.1.1.

Macbook Ventura 13.4.1

 

Screenshot 2023-07-20 at 16.39.46.png

  • Staff
Posted

Hi Iceritchie,

Please could you upload a copy of the file to the following DropBox link so I try and get this recovered for you? Please note this process can take some time so if the file is time sensitive I would advise starting again from scratch I apologise for any inconvenience this causes you and recommend making back ups of any important files in the future.

https://www.dropbox.com/request/Jw9tOBiHc5mG2Px0QUJ0

Thanks
C

Please tag me using @ in your reply so I can be sure to respond ASAP.

Posted
6 minutes ago, Callum said:

Hi Iceritchie,

Please could you upload a copy of the file to the following DropBox link so I try and get this recovered for you? Please note this process can take some time so if the file is time sensitive I would advise starting again from scratch I apologise for any inconvenience this causes you and recommend making back ups of any important files in the future.

https://www.dropbox.com/request/Jw9tOBiHc5mG2Px0QUJ0

Thanks
C

Thank you. I have uploaded the file. 

Posted
49 minutes ago, MikeTO said:

Have you tried restarting macOS to see if that releases the lock on the file?

The OP wrote in the first post that  "(Mac shutdown along with all apps to prove)" so I think that already had been tried.

All 3 1.10.8, & all 3 V2.6 Mac apps (currently 2.6.4); 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
A
ll 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

  • 1 month later...
Posted

I had to restart the file after this issue which took about a week to catch up. I have since started making backups of the Wii file. However I have had the same problem now on a new project new file. The difference is I managed to 'save as' the recovery file before getting to the totally corrupt point.

 

Posted

Did you try:

  1. Making a copy of the file and trying to open the copy?
  2. Placing one page of the file into a blank document of the same size using File > Place?
  3. Adding pages from the file using Document > Add Pages from File? Try a couple of single pages if the whole thing doesn't work.

Good luck

Posted
3 minutes ago, MikeTO said:

Did you try:

  1. Making a copy of the file and trying to open the copy?
  2. Placing one page of the file into a blank document of the same size using File > Place?
  3. Adding pages from the file using Document > Add Pages from File? Try a couple of single pages if the whole thing doesn't work.

Good luck

I managed to recover the file with only a few edits missing. Couldn't save. Therefore managed to do a save-as, then back up the file. I couldn't do this in my first experience of this problem as the file became corrupt. With this project I seem to have caught it early and therefore grabbed a backup. I have now deleted my original and will be using the saved-as version. Thanks for the help Mike. Regards Neil.

  • 1 year later...
Posted

Just wondering if people are experiencing this. I am still getting it on occasions. Not often, but its a relevant and critical issue for me. Im getting by as i manually backup my projects now every couple of days. However it's still a topic and one which does give me concerns about whether Affinity is reliable enough to continue using it. Happened over the past 12 months 5-6 times.

Posted
7 hours ago, iceritchie said:

i manually backup my projects now every couple of days.

In general, this is an obvious and highly recommended technique if you are working on important data - assuming 100% functionality and reliability of any HW (PC, disk) and SW (OS, applications) is definitely not worth it.

Are you working on local disks, or on some generally not recommended external one (usb, cloud, nas)?

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.5.7.2948 (Retail)
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 24H2, Build 26100.2605.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 24H2, Build 26100.2605.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Posted

Working on local drive. This then automatically replicates the folders to a cloud drive. So if the file gets corrupt it gets backed up too.hence I now manually backup too. But I have no other apps that have corrupted my working docs. I’m seeing too many crashes too meaning reopening a crash saved file. But this is a separate issue.

Posted
8 hours ago, iceritchie said:

Working on local drive. This then automatically replicates the folders to a cloud drive.

This is not true "local". If you are working on cloud folders that are local but are also managed by a cloud management (application/OS), this can cause problems - the file is managed by Affinity and the cloud at the same time. Personally, I would never work this way - I recommend saving/working locally (e.g. a personal documents folder), and saving to the cloud (to a cloud folder) only for backup and sharing.

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.5.7.2948 (Retail)
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 24H2, Build 26100.2605.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 24H2, Build 26100.2605.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Posted

Ive been using for the last few days a local copy only. And started to move other projects away from automatic cloud sync. I'm still getting 'Open recovery file?' requests more often than I should. I haven't yet had a corrupt file issue since moving (although I did have one yesterday after unlinking a cloud but still connected to iCloud). This is happening even after I have saved the file normally, closed things down then reopened for another session a few hours later. Most times it's ok, but the open recovery file request on previously saved files signals something isn't right to me. Im going to have to make some choices whether to stick with it for next update, regress to an earlier update or ditch Affinity and back to Adobe.

×
×
  • 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.