TerrenceH Posted January 23 Share Posted January 23 (edited) Hello, Desktop is Mac Studio, M1 Max, 32GB, Sonoma 14.3 I am experiencing a strange glitch. Publisher 2.3.1 crashed (spinning wheel of death). After 5 -10 minutes had to do a force quit. When it restarted, it gets to the screen that says "Checking license configuration", and subsequently is stuck. Then (spinning wheel of death). - need to force quit. Here is what I have tried to do to fix it: Restarted Mac: Publisher advances to same point on checking license and stops Downloaded fresh copy - reinstalled over top of existing copy: Advances to same point on checking license and stops Removed references to Publisher in Mac Security settings and deleted Publisher. Reinstalled Publisher: Same result as before, stuck on checking license Both Designer 2.3.1 and Photo 2.3.1 load fine. I even tried opening Designer first, then Publisher, but the result is the same. Have I missed any troubleshooting steps here? I'm scratching my head trying to figure this out!!! Edited January 23 by TerrenceH adding information Quote Link to comment Share on other sites More sharing options...
v_kyr Posted January 23 Share Posted January 23 Just by opening the app itself (so with no doc opening at all), or when opening it with some doc? - For the later see related ... Did you also already tried to reset the app defaults? Other than that is "Metal" computing enabled under the performance options (?), though from your above description you might not be able to reach so far at all state wise, in order to check for that setting. Quote ☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan ☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2 Link to comment Share on other sites More sharing options...
TerrenceH Posted January 23 Author Share Posted January 23 V_KYR, Thank you for the input! This was occurring when opening the app itself only. Publisher had been working fine on Sonoma up until this. I tried opening from a file, and got the same results. I was going to reset to default earlier, but wrongly assumed that by reinstalling I would bypass any other troubles. So, by your suggestion I did that, and now it is working fine. Problem solved. Thank You! v_kyr 1 Quote 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.