Jump to content

Affinity Publisher v1 on macOS SONOMA 14.0 bugs


Tanya Y.

Recommended Posts

Hi,

after upgrade on Sonoma 14.0 I'm constantly getting the following bugs:

*since the issue with the light UI is already known I won't include it here. Other problems I've had during work:

1. Some keyboard shortcuts don't work: e.g. I have set the Next page shortcut to cmnd+down arrow >> it doesn't work. If I change it a combination of cmnd + any number >> it does work. I've tried over 20 different combinations and none of them worked (except cmnd+number).

2. Apply master function - after the menu to select which master to apply pops up, selecting any master page is not possible so the action cannot be completed (video attached).

Link to comment
Share on other sites

I can duplicate both of these bugs.

As a workaround for the second one, drag the master page thumbnail onto the page (or selected pages) thumbnails you want to apply it to. This will replace the existing master and not give you an opportunity to add it to the existing master, but at least you can apply it.

I also recommend upgrading to v2 - Publisher v2 is far more powerful than Publisher v1.

Link to comment
Share on other sites

  • Staff
18 hours ago, Tanya Y. said:

1. Some keyboard shortcuts don't work: e.g. I have set the Next page shortcut to cmnd+down arrow >> it doesn't work. If I change it a combination of cmnd + any number >> it does work. I've tried over 20 different combinations and none of them worked (except cmnd+number).

2. Apply master function - after the menu to select which master to apply pops up, selecting any master page is not possible so the action cannot be completed (video attached).

Thanks for reporting these.

We already had the shortcut issue logged but didn't have the Apply Master Page issue logged, so I've just logged that with the Developers :) 

Link to comment
Share on other sites

  • 3 weeks later...
  • Staff

The issue "Text Key Keyboard Shortcuts do not function on macOS Sonoma" (REF: AF-508) has been fixed by the developers in internal build "2.3.0.2083".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.

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.