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.

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?

Misaki Nothing I can think of.
I also have not faced this bug since I posted this but I'll try to reproduce it and capture my screen while doing so.