I've been getting this surprise lately... Do you?

[albertkinng]

When I get this I just quit the app and re-launch it and my life goes on, but I was wondering if you guys are having this issue too.

The only thing I did recently was add a bunch of gradients (V1) from an old archive. Does that have something to do with this issue?

[walt.farrell]

9 minutes ago, albertkinng said:

The only thing I did recently was add a bunch of gradients (V1) from an old archive.

How many is a "bunch", and where did you add them?

[albertkinng]

@walt.farrell Oh, 68 palettes and add it with the import palette option on the swatches window. Why? You think that may be the problem? Is there a limit?

[walt.farrell]

I don't know for sure that it is related, but given that the V2 apps share that kind of data, and coordinate updates to it, it's possible it could be related. Especially as the problem started after you added the palettes.

 

[carl123]

Similar post, yesterday

 

[albertkinng]

Oh wow...

[Dan C]

Hi @albertkinng,

Thanks for your report and our sincerest apologies for the delayed response here. We are exceptionally busy following the release of V2 and we thank you for your continued patience and understanding here.

The users in the above thread are reporting this issue for Windows and my colleague is investigating issues with OpenCL Hardware Acceleration there, however this would not apply to the macOS version of the Affinity apps.

I note that one user in the above thread has been loading, editing and saving files on a server - are you editing files from an external or cloud source etc please?

[albertkinng]

2 hours ago, Dan C said:

are you editing files from an external or cloud source etc please?

Yes, all my work is on external drives. I have used a project manager network app to access my document files for a long time now. Never had a problem until now. Main drives are on an external dock and others are on a shared cloud such as Google Drive, Dropbox and so on. (I'm running a Mac Mini M1 / 16g RAM with latest Ventura OS)

Edited February 28 by albertkinng
Mac info added

[Dan C]

Thanks for confirming that for me  - I've been testing this further and the only way I'm able to see this occur is if one Affinity app is in a 'not-responding' state, then I try to launch a different Affinity app.

Did this by chance occur when the app was 'not-responding' or the 'spinning wheel' was shown for your cursor?

If not, we can enable some further logging, to provide our team with more information when this occurs. Can you please:

1. Open terminal and type the following, then hit enter:
   launchctl setenv AffinityIpcVerbose 1
    
2. With Terminal open, launch the Affinity app and wait for this error to appear
3. Depending on where the Affinity app was installed from, navigate to the following location:
   MAS: ~/Library/Containers/Affinity Designer 2/Data/Library/Application Support/
   Affinity Store: ~/Library/Application Support/Affinity Designer 2/
4. In this folder you should see the ipc.log file, please attach a copy of this to your reply here.

Many thanks once again