• Editor
  • OS X 1.1.0 won't launch - here's a fix.

Thank you for the quick response 🙂

I was able to start Spine from the terminal using your suggestion. (I had to give the complete path and add the Spine/ directory the default installer uses, like this: )

java -server -jar /Applications/Spine/Spine.app/Contents/MacOS/launcher/launcher.jar 

I was able to enter my license number at the splash screen, and Spine proceeded to download a newer version. Unfortunately, it failed when the progress bar reached the end:

Apollo:~ log$ java -server -jar /Applications/Spine/Spine.app/Contents/MacOS/launcher/launcher.jar 
Spine Launcher 1.0.03-full
Mac OS X i386 10.6.8
Updated to: 1.1.04
Uncaught
java.lang.NoSuchMethodError: java.net.URLClassLoader.close()V
	at com.esotericsoftware.spine.editor.launcher.Launcher.f(SourceFile:250)
	at com.esotericsoftware.spine.editor.launcher.Launcher.e(SourceFile:570)
	at l.e.run(SourceFile:556)

I hit ctrl+c at the console to break, and re-ran Spine, which now opens a pop-up error, with this at the console:

Spine Launcher 1.0.03-full
Uncaught
java.lang.NoSuchMethodError: java.net.URLClassLoader.close()V
	at com.esotericsoftware.spine.editor.launcher.Launcher.f(SourceFile:250)
	at com.esotericsoftware.spine.editor.launcher.Launcher.<init>(SourceFile:207)
	at com.esotericsoftware.spine.editor.launcher.Launcher.main(SourceFile:671)

My spine.log is:

Spine 1.0.18-full
Licensed to: [EDIT: Removed]
Mac OS X i386 10.6.8
ATI Technologies Inc.
ATI Radeon X1600 OpenGL Engine
2.0 ATI-1.6.36
Java 1.6.0_41
Apple Inc.
Java HotSpot(TM) Client VM
Started.

As you can see my system's version of java is 1.6, which I'm guessing is the root of the problem with the new network calls.

Related Discussions
...

Hmm, wow URLClassloader is really bad prior to Java 7, no good, for sure way to clean up the resources it uses... I've rewritten a portion of the launcher so it works fine on Java 6. I don't really feel like repackaging the whole Mac stuff at 4:30am, so I will PM you the file you need.

Thank you, I really appreciate the fix (PM response sent.) It works great!

I'm having exactly the same problem as Logarhythm.

When will a fixed build be out?

New build for the launcher is up. Note the JAR is now named launcher-full.jar, so the name in the command above needs to be changed.

Actually I decided I can do better than that... just updated again. Now it should run using the system Java if it detects the OS is 32bit. Can you guys try downloading the latest launcher and see if it runs on your 32bit Mac just by clicking the Spine.app?

I just downloaded/installed the latest launcher, and Spine runs when clicking the .app again. Thanks again.

Great! Thanks for trying it out. 🙂

I'm still getting the "Install X11" prompt. Am I missing something? Spine used to run just fine.

Are you able to install the X11 stuff? Should work after that.

I don't want to, to be completely honest. Spine is the only app that (now) needs it, and I like to keep my OS as clean as possible. The required download is 66Mb, which will expand to considerably more. This seems more than a little excessive just to run Spine.

So I'm left in a position where Spine no longer runs on my system. When I pledged on Kickstarter, the trial worked just fine (i.e. no X11 requirement). The previous versions worked just fine too. Hmmm...

Then use the command I posted to run it. :think:

java -server -jar /Applications/Spine/Spine.app/Contents/MacOS/launcher/launcher-full.jar

Well, I made it a little easier to use an alternate Java. If you define an environment variable called SPINE_JAVA, it will use that when Spine.app is run. To use the system Java, you'd set it to "java" (without quotes). Eg, from the command line...

export SPINE_JAVA=java
open Spine.app

There are various ways to set environment variables in OS X:
http://stackoverflow.com/questions/1356 ... es-in-os-x
You can use the RCEnvironment tool if you want a GUI for doing it:
http://www.rubicode.com/Software/Bundle ... nvironment

Thanks Nate. That's a cleaner solution, and one that I'm happy with.

Sorry Nate - I've added the environment variable (using the GUI tool you linked to), but I'm still getting the X11 prompt. I've rebooted, just to be sure the variable was active.

I'm running Spine v1.1.0.7, in OSX 10.8.2.

Any ideas?

Hmm. If you open the Console app, do you see a message from Spine when it starts? It should say "Spine: Using Java: xxx" where xxx is the SPINE_JAVA you set. What happens if you try:

export SPINE_JAVA=java
open /Applications/Spine.app

If that doesn't work, then I don't think you have the latest Spine launcher, you should download it again. If that works then it means however you are launching Spine isn't seeing your environment variable. I've read that launching via Spotlight may not see your variable:
http://www.digitaledgesw.com/node/31

I'm definitely running the latest build (I just re-installed to be sure).

Even when I run those commands, I'm still presented with the X11 prompt. Weird.

I can see the SPINE_JAVA entry in my exports:

...
declare -x SHELL="/bin/bash"
declare -x SHLVL="1"
declare -x SPINE_JAVA="java"
declare -x SSH_AUTH_SOCK="/tmp/launch-65LXli/Listeners"
declare -x TERM="xterm-256color"
...
Nate a écrit

If you open the Console app, do you see a message from Spine when it starts? It should say "Spine: Using Java: xxx" where xxx is the SPINE_JAVA you set.

^
|

If you just want to get it working, you can right click Spine.app, Show Package Contents, expand Contents/MacOS, and edit run.sh with TextEdit. Where it says:

"$SPINE_JAVA" \

Check that to:

java \
Nate a écrit

If you open the Console app, do you see a message from Spine when it starts? It should say "Spine: Using Java: xxx" where xxx is the SPINE_JAVA you set.

I didn't understand what you meant by "console". Are you referring to terminal? If so, I don't see that text, no.

By Console app I mean an app that comes with OSX called Console. You can find it by clicking Spotlight (the magnifying glass in the upper right of the screen) and typing console.

However, I found a problem in another thread... the builds I've been pushing don't actually have the changes they should. If you could please download the launcher again, I think you'll find it works. Sorry about this mess! :bang: