Jump to content

Recommended Posts

Posted

I previously used a template to create a photo collage. I saved and printed no problem. I started a new template with new pictures and after the first 2 pictures it crashed. I updated my Mac OS to 11.3 ( somewhere I read it could be my graphic drivers). After the update it still crashing. I have no idea how to fix this.

 

Below is the error message I received. I do not know what this means.

Last login: Wed May  5 21:15:06 on console

 

The default interactive shell is now zsh.

To update your account to use zsh, please run `chsh -s /bin/zsh`.

For more details, please visit https://support.apple.com/kb/HT208050.

/Applications/Affinity\ Publisher.app/Contents/MacOS/Affinity\ Publisher ; exit;

Janices-MacBook-Air:~ JaniceHenderson$ /Applications/Affinity\ Publisher.app/Contents/MacOS/Affinity\ Publisher ; exit;

2021-05-07 18:10:29.827 Affinity Publisher[5641:222885] CoreText note: Client requested name ".SFNS-RegularItalic", it will get Times-Roman rather than the intended font. All system UI font access should be through proper APIs such as CTFontCreateUIFontForLanguage() or +[NSFont systemFontOfSize:].

2021-05-07 18:10:29.828 Affinity Publisher[5641:222885] CoreText note: Set a breakpoint on CTFontLogSystemFontNameRequest to debug.

2021-05-07 18:14:04.254 Affinity Publisher[5641:222885] *** WARNING: Method convertPointToBase: in class NSView is deprecated on 10.7 and later. It should not be used in new applications.

Posted

Hi @J SIppio,
welcome to the Affinity forums!

Where/how did you receive  this message?
It doesn't look like an Affinity message nor like a macOS crash report. (and its first date "Last login May 5" was before the dates below "2021-05-07")

The first entry concerns a system font "SNFS". I am not sure if it's related to your crashes but it might influence or be an issue anyway. There appears to be a confusion in the font data base noticed by Affinity, a font name should not start with a . (dot, full stop) as in ".SNFS". – So you could try resetting the font cashes of either macOS and/or APub. In this post + three posts later is How-To:

Make sure after resetting the macOS font cash to reboot, or at least to logout + login.

Alternatively you could shut down Affinity apps + boot your mac in safe mode (hold the Shift-key until the apple appears, it takes some time to boot and works with reduced speed). This also might reset the macOS font cash. You also should be able to launch APub in this mode.

• MacBookPro Retina 15" |  macOS 10.14.6  | Eizo 27" | Affinity V1  
• iPad 10.Gen.  |  iOS 18.5.  |  Affinity V2.6

Posted
21 hours ago, thomaso said:

Hi @J SIppio,
welcome to the Affinity forums!

Where/how did you receive  this message?
It doesn't look like an Affinity message nor like a macOS crash report. (and its first date "Last login May 5" was before the dates below "2021-05-07")

The first entry concerns a system font "SNFS". I am not sure if it's related to your crashes but it might influence or be an issue anyway. There appears to be a confusion in the font data base noticed by Affinity, a font name should not start with a . (dot, full stop) as in ".SNFS". – So you could try resetting the font cashes of either macOS and/or APub. In this post + three posts later is How-To:

Make sure after resetting the macOS font cash to reboot, or at least to logout + login.

Alternatively you could shut down Affinity apps + boot your mac in safe mode (hold the Shift-key until the apple appears, it takes some time to boot and works with reduced speed). This also might reset the macOS font cash. You also should be able to launch APub in this mode.

Thank you I will try the suggestions.

  • 1 year later...
Posted

Hi both, J Slppio, wondering if the suggestions worked as i have the same problem. Affinity crashes as soon as I get to a certain page in my document. The Terminal message is as above:

All system UI font access should be through proper APIs such as CTFontCreateUIFontForLanguage() or +[NSFont systemFontOfSize:].

Is there a permanent fix to this?

Thanks in advance

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.