Unfortunately, updating macOS doesn't fix the issue.

I've managed to launch Spine 3.8.99. I get the same "antivirus" error message, but the app launches. However, it is useless to me as I need 4.1.x

4.1.24 displays the error message but the app does not launch.

I've tried previously suggested solutions (like disconnecting external monitors, etc). I have a Mac Studio, so all monitors are external. But I have two, so I disconnected one, it didn't work. I switched to the other screen, same result. So now, I'm stuck.

Sorry for the trouble. Can you try deleting your settings like described here?

https://esotericsoftware.com/forum/d/25580-spine-2d-crash-issue/10

Mario already tried that. Without success

Another weird thing. I have the same hardware at home (once again Mac Studio M1 Max, macOS 14.4) and Spine 4.1.24 starts without an issue. I don't know where the problem lies, but that's weird.

I'm frankly out of ideas regarding this issue. The only thing I can think of is some software interferring with Spine somehow, that's installed on the "problematic" mac, but not on your mac at home.

Could you maybe check what software runs on each mac?

I also started getting this error a few days ago when I started using an external monitor.

I have been able to reproduce it a couple of times by opening Spine on the monitor screen instead of the screen of my Macbook. If I open Spine on my Macbook screen, it works as expected, but if I open it on the external monitor, I get that error. That behaviour has not been consistent though.

To fix it, I usually have to wait for sometime and open it on my Mac screen.

marvfash I also use a MacBook and an external monitor, but have never gotten antivirus error messages. Although older versions like 3.8 sometimes crash when moving the window to an external monitor.
What version of Spine were you trying to run?

Misaki I'm using 4.2.14, the latest version.

marvfash Thanks for your reply! I have tried the followings but could not reproduce the problem:

• Move the Spine 4.2.20 window to an external monitor immediately after launching it on the MacBook screen.
• Set the external monitor as the main display and launch Spine 4.2.20.
• Mirror the MacBook screen on the external monitor and launch Spine 4.2.20.

(4.2.20 is currently the latest version.)
I tried each method about 3 times each. I tried launching Spine directly and launching it by opening a Spine project, but unfortunately I could not reproduce the problem.
I would like to reproduce the problem, but the conditions still seem to be lacking. Is there anything else specific to your environment?

abuki Thanks for your report! It's good to hear that it's already working, but I'm sorry that it doesn't seem to help us reproduce the problem... Is your macOS version still 14.1.2?

abuki

I am currently on 14.4.1

Hmmm, I see.

Yes, it is good to know that disconnecting the external monitor seems to be an effective workaround.

Just wanted to add that I am also running into this issue, even without an external monitor connected.
I tried deleting settings and other suggested fixes but nothing was working.

Finally, I tried changing my computer's display resolution and opening Spine while using the lower resolution and that seems to have worked. I was then able to change the resolution back to normal and it seems to be working now.

It definitely seems like there is some issue with the graphics initialization on mac. For reference I'm using an MacBook Pro with an M2 Max with 38 core GPU and 32GB ram, running Sonoma 14.5.

samanabo Perhaps I spoke too soon. It seems this workaround only worked once. I'm currently unable to open Spine again.

samanabo I'm sorry to hear you're having trouble. Could you post the spine.log file to this thread? It should have been created at the following location:
~/Library/Application Support/Spine/spine.log

Misaki Here is my log file. I have another possible cause... Spine seems to only crash when I have a PS4 controller plugged in. If I unplug the controller then it launches fine.
Is it possible this is caused by the audio device in the ps4 controller?

samanabo Thank you for submitting the spine.log! We have not solved the problem yet, but we have found something that we think may be the cause and are investigating it. We will let you know when we have resolved the issue.