FileBot

After upgrading to Filebot 4.1 and installing the required Oracle Java 8, the filebot script for the "Fully Automated Media Center with Transmission (Mac)" stopped working.

The first error I was getting was "missing file" for the file /Applications/Filebot.app/Contents/MacOS/filebot

So I opened the Filebots.app package and couldn't find a "filebot" file in there . . .

So I tried pointing the script to the filebot.sh file instead, at /Applications/Filebot.app/Contents/MacOS/filebot.sh

But this brings up a new set of errors:

---------------------------------

Exception in thread "main" java.lang.UnsupportedClassVersionError: net/filebot/Main : Unsupported major.minor version 51.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:637)
at java.lang.ClassLoader.defineClass(ClassLoader.java:621)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)
at java.net.URLClassLoader.access$000(URLClassLoader.java:58)
at java.net.URLClassLoader$1.run(URLClassLoader.java:197)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)

---------------------------------

What have I done wrong?

Do I need to change the script more, or is it a problem with the latest Java installation?

The script was working amazingly well for me prior to upgrading to Filebot 4.1.

RE:
http://www.filebot.net/forums/viewtopic ... =520#p3470

According to the error message it's running with Java 6 and not Java 8. Probably since the default java is still set to the default installed Mac Java 6.

Thanks for pointing that out! You were right. The odd thing is that under the Mac's System Preferences -> Java Preferences it was showing that Java 8 was installed and the default. But then when I ran java -version in Terminal it only showed Java 6, no 8.

I tried a few different methods for resetting the Java default with no luck. Tried rebooting, no luck . . . But then I just tried re-installing Java 8 a few more times in a row. On the third attempt something "clicked," for an unknown reason, luckily -- and now Java 8 is the new default when I run java -version in Terminal.

Once that was finally working, the Filebot transmission-postprocess script started working like a charm again. Perfect!

One thing I should note, though, in case anyone else is looking at this thread for help later:

After updating to Filebot 4.1, and even after Java 8 was really finally working as the default, the script as described at http://www.filebot.net/forums/viewtopic ... =520#p3470 still failed for me if I left MacOS/filebot in the code -- but the script works fine if I add the ".sh" to the code, so it's:

/Applications/Filebot.app/Contents/MacOS/filebot.sh

Hi,

I am experiencing the same issue on Mavericks 10.9.3:

This is the version of Java: And these are the error messages for both filebot (available after running ./install.sh) and /Applications/FileBot.app/Contents/MacOS/filebot.sh:
Can you please help working this around?

Thanks and kind regards,

Cristian

As you can see in the Terminal java is still linked to the Java 6 runtime. Try removing Java 6 completely and see what happens, or Google on how to set Java 8 as default framework.

I fixed this by installing the latest SDK... seems like installing the JRE messes JAVA somehow, as I am not a developer I wouldn't know how or why. But installed the SDK v8 and fixed it right away... I did uninstall (moved to trash) the JRE plugin files as explained in java.com and then re-enabled the older Java 6 (by following http://support.apple.com/kb/ht5559) .

This is what the java -version shows now:
java version "1.8.0_05"
Java(TM) SE Runtime Environment (build 1.8.0_05-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.5-b02, mixed mode)

Hope this helps anyone else experiencing this issue.

Cheers!