@geowal-wondeluxe thank you for the logs. Based on those, I can infer that Spine crashes when you click "Start" in the launcher window and the window is closed (crashes in glfwTerminate). So that checks out with what you told us earlier.

Sadly, apart from this confirmation, the log doesn't give me any clues on why closing the launcher window would crash.

Could you please try launching 3.8.99?

What Mac hardware do you use? Are you using an external monitor and have you moved the Spine window to that monitor previously?

Is there something I should be looking for in launching 3.8.99? As mentioned earlier, Spine is now starting as expected (both 3.8.99 and 4.1.24). So I have no way of reproducing the issue.

I'm using a Mac Mini (2018):
3.2 GHz 6-Core Intel Core i7
Intel UHD Graphics 630 1536 MB

I have a single monitor plugged in through HDMI: Dell U2717D

Seems like some proper voodoo stuff that it would suddenly stop, then start working again.

Apologies, I missed that it started working again for you. Since it's a mac Mini it's super puzzeling. The issue you saw might sometimes be related launching Spine on a MacBook with an external monitor. It happening in a mac Mini is very, very strange.

That said, the mini you have is the same I have, and its Intel GPU and context management driver is notoriously bad. I've spent quite a bit of time debugging issues related to that in both Spine and other apps, and the conclusion was usually to throw my hands in the air, because I can not fix bugs in the drivers myself :/

Mario all good! Thanks for taking the time to look into it. I just figured it was worth bringing up because it seemed like there were enough users experiencing the problem. It certainly is annoying, but if there's nothing that can be done then throwing hands in the air is definitely an appropriate response!

This annoyingly has cropped up again for me.

I launched 3.8.99 to see if anything else happens and it did! I still receive the same error message about antivirus software, but after dismissing it, Spine launches anyway. I appear to be able to start a new project and save.

The other thing I've noticed, which may or may not be related is launcher-1.json in ~/Library/Application Support/Spine/settings/ is saved in an unrecognisable text encoding (or binary) according to VS Code. I've tried to open it in a couple of text editors but had no success.

geowal-wondeluxe Sorry to hear that the problem has recurred.

The other thing I've noticed, which may or may not be related is launcher-1.json in ~/Library/Application Support/Spine/settings/ is saved in an unrecognisable text encoding (or binary) according to VS Code. I've tried to open it in a couple of text editors but had no success.

The fact that this file cannot be opened should have nothing to do with this problem. This file stores the activation code for the computer's Spine installation, so it cannot be read by a normal text editor.

I'd like to reproduce this problem, are there any other conditions you can think of?

The fact that this file cannot be opened should have nothing to do with this problem. This file stores the activation code for the computer's Spine installation, so it cannot be read by a normal text editor.

No problem, I wasn't sure. I was looking for the flag to disable automatic start and couldn't remember which file it was in.

I'd like to reproduce this problem, are there any other conditions you can think of?

Sorry, I can't. I'm really at a loss. And of course now it's working again. I haven't changed anything since I last tried to open it. All other running software is the same. Computer hasn't been to sleep.

I was hoping that 3.8 ran might provide a clue.

Hello,

having this issue with Spine 4.2 beta from a few days ago and can't open the app anymore :-( I tried everything.

I'm on macOS 14.3.1.

We are at a bit of a loss, as we can't reproduce the problem. The users above who couldn't run on macOS later could, apparently without know what changed. I hate to suggest voodoo, but have you tried rebooting?

I'm sorry to not be able to add more information about this issue as is really weird. I restarted and didn't solve the issue, BUT I shutdown the computer and when I start everything again and open the launcher with the same version of Spine... It's works!!! If I find something more related to this I'll let you know.

Thanks!

ceegee Thank you very much for the information! I am also using macOS Sonoma but I've never encountered the problem that some users have reported here, so it's helpful to hear from people who have.

@ceegee when you say, you "had this issue" does that mean Spine is working for you again? This is so mysterious. I have two Apple machines both running the latest Sonoma and I've never ever seen anything like you describe. And I regularly use the USB-C to connect and disconnect external monitors, as I move between the office and home office daily. I can't remember being prompted to approve a connection (with or without Spine) ever.

Mario Yep! Spine is working again thank you. Your advice about unplugging external monitors saved me.

Same problem here on macOS 14.3.1. Problem appeared on earlier version on the system, then disappeared, then came back today.

I've attached the log file, but I suppose it won't provide any useful information.

I've tried both the Intel and Apple Silicon version (using a Mac Studio M1 Max).

macOS 14.4 is available so I will try to update the system to see if anything changes.

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.