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

Can't run Publisher, Continual Spinning Rainbow


Recommended Posts

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.

Link to comment
Share on other sites

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

macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1

Link to comment
Share on other sites

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?

Link to comment
Share on other sites

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.

macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1

Link to comment
Share on other sites

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

  1.  I duplicated the file
  2. I changed the file name to one word. Before it was "Trace and Learn Hieroglyphics.afpub" including the spaces. I renamed it "Hieroglyphics.afpub"
  3. I opened the file
  4. It also opened one that had crashed alongside it in recovery mode
  5. The renamed file is now working fine
  6. Could the issue be with having spaces in the file name?

If you're still interested in seeing the broken file, let me know.

Link to comment
Share on other sites

7 hours ago, SueWAuthor said:
  1. Could the issue be with having spaces in the file name?

 

Mac OS has always allowed spaces in "File Names.txt"

 

Mac Pro (Late 2013) Mac OS 12.7.4 
Affinity Designer 2.4.1 | Affinity Photo 2.4.1 | Affinity Publisher 2.4.1 | 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

  • 2 weeks later...

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.