SueWAuthor Posted August 29, 2020 Share Posted August 29, 2020 Hello, This is the second time this has happened to me in a matter of months. I'm on a MacBook Pro running the latest version of Publisher. It has corrupted my file and whenever I launch, it shows the broken file with almost all of the pages missing, and then freezes and goes to the spinning rainbow of death. As I said, it corrupted an earlier file in the exact same way a few months ago. At present, I cannot open any files at all in the program because it keeps trying to recover the file it broke. It opens and freezes. Fixes I have tried that have not worked: rebooting renaming the file (it still finds it) duplicating the file and throwing away the original (it finds the duplicate and tries to open it) dragging the file to the desktop (it still finds it and tries to open it) I can no longer use the program to work on any of my files at all. Publisher just keeps trying to open that file and freezing. As a side note, that file represents 6 months worth of work, so I'm pretty frustrated. (I managed to find a fix back in June when it happened, but I don't remember what I did) Suggestions? Thank you. Quote Link to comment Share on other sites More sharing options...
thomaso Posted August 29, 2020 Share Posted August 29, 2020 Just an idea: To avoid previous files getting opened you could try to rename the according preference folder (inside your user Library) to prevent APub from using it and its nested "autosave" folder. Affinity Store version: ~/Library/Application Support/Affinity Publisher Apple Store version: ~/Library/Containers/com.seriflabs.affinityPublisher Quote macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1 Link to comment Share on other sites More sharing options...
SueWAuthor Posted August 29, 2020 Author Share Posted August 29, 2020 3 hours ago, thomaso said: Just an idea: To avoid previous files getting opened you could try to rename the according preference folder (inside your user Library) to prevent APub from using it and its nested "autosave" folder. Affinity Store version: ~/Library/Application Support/Affinity Publisher Apple Store version: ~/Library/Containers/com.seriflabs.affinityPublisher Thanks for the suggestion, thomaso. Under containers, there's no com.seriflabs.affinityPublisher that I could find. I did find this folder called com.seriflabs.affinitypublisher.savedState under saved application state. Per your suggestion, I renamed that and it opened the program without the file opening, yay! Thank you. But the file is still broken. I opened it and once again got the spinning wheel of death. Suggestions there? Quote Link to comment Share on other sites More sharing options...
thomaso Posted August 29, 2020 Share Posted August 29, 2020 Good to hear you managed to make APub open again without previous documents. Unfortunately I don't know how Affinity temp files are stored in the MAS version. If you have macOS TimeMachine active you might want to copy an earlier state of the related temp file(s) for a later restore. Possibly a Serif moderator will offer to take a look to your corrupted document and maybe able to fix it. Quote macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1 Link to comment Share on other sites More sharing options...
SueWAuthor Posted August 29, 2020 Author Share Posted August 29, 2020 Thanks again, thomaso Quote Link to comment Share on other sites More sharing options...
Staff Jon P Posted September 1, 2020 Staff Share Posted September 1, 2020 Can you upload the document here and we'll take a look. Thanks! Quote Serif Europe Ltd. - www.serif.com Link to comment Share on other sites More sharing options...
SueWAuthor Posted September 3, 2020 Author Share Posted September 3, 2020 Thanks, Jon P -- so just now I decided to try one last thing and I was able to open the file. I'm not sure which piece of what I did worked, but I duplicated the file I changed the file name to one word. Before it was "Trace and Learn Hieroglyphics.afpub" including the spaces. I renamed it "Hieroglyphics.afpub" I opened the file It also opened one that had crashed alongside it in recovery mode The renamed file is now working fine Could the issue be with having spaces in the file name? If you're still interested in seeing the broken file, let me know. Quote Link to comment Share on other sites More sharing options...
Old Bruce Posted September 3, 2020 Share Posted September 3, 2020 7 hours ago, SueWAuthor said: Could the issue be with having spaces in the file name? Mac OS has always allowed spaces in "File Names.txt" Quote Mac Pro (Late 2013) Mac OS 12.7.6 Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5 | Beta versions as they appear. I have never mastered color management, period, so I cannot help with that. Link to comment Share on other sites More sharing options...
SueWAuthor Posted September 12, 2020 Author Share Posted September 12, 2020 so, the file is broken again... Quote Link to comment Share on other sites More sharing options...
Staff Jon P Posted September 14, 2020 Staff Share Posted September 14, 2020 I'll take a look, if you can upload to the above link again so I'm looking at the latest version that'd be helpful! Thanks Quote Serif Europe Ltd. - www.serif.com Link to comment Share on other sites More sharing options...
Recommended Posts
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.