1.12(.2) crashes on macOS

[Proplex]

Hey there, loving this launcher. Interesting problem with macOS, and it's due to a missing library. I've created an empty 1.12.2 pack for users who which to play basic vanilla and it works great on Windows--but it seems on macOS it's crashing because of a missing library required for the new narration functionality. Through the Mojang client, it works fine.

Here's the client crash summary:

Caused by: java.lang.ClassNotFoundException: ca.weblite.objc.NSObject
	at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
	... 19 more

Although it works fine through the Mojang launcher (for me), some quick Googling of this issue shows that other people have experienced it: https://bugs.mojang.com/browse/MC-118506

It seems like an edge case since the report is rare and Mojang hasn't addressed it at all.

I notice that the Launcher is fetching the .jar from the enumerated libraries list:

[info] Fetching ca/weblite/java-objc-bridge/1.0.0/java-objc-bridge-1.0.0-natives-osx.jar from [https://libraries.minecraft.net/ca/weblite/java-objc-bridge/1.0.0/java-objc-bridge-1.0.0-natives-osx.jar, http://togame.ipwnage.com/launcher/libraries/ca/weblite/java-objc-bridge/1.0.0/java-objc-bridge-1.0.0-natives-osx.jar]

But it seems like a futile effort since it crashes.

I've tried building the vanilla pack with the java-objc-bridge-1.0.0.jar in ./src/libraries/ca/weblite/java-objc-bridge/1.0.0 but that doesn't seem to help either.

Any ideas? I've hit a wall here.
Here's the full Launcher log (with download output + launch crash): https://ipwnage.com/stuff/vanilla_crash.txt

[kozlek]

Hey ! I have currently the same problem. I made some tests like adding the library in the folder, then add it in the manifest file, but it keeps failing... I think we have to dig in the code to see where the librairies are downloaded, to add the missing one.

[jwulf]

I have the same problem.

I've tried copying java-objc-bridge-1.0.0.jar to .modpacks/staging/launcher/libraries/ca/weblite/java-objc-bridge/1.0.0

Same result - crashes.

[panwolfram]

I've got the same error, with 1.12.1. I can't figure out how to connect this library to my modpack...

[gailingmic]

yes this error still exists...

this seems kinda related:
MinecraftForge/MinecraftForge#3964

especially the post:

Wow...... The native for mac is packaged in the main jar as a compiled dylib file.
That is why I cannot find the jar on any maven repo because it is totally unnecessary. LOL

seems like we have to add a check in installLibraries to filter the Mac native out!

[DaMatrix]

Can confirm, a number of my users are unable to launch because of this.

[jkroepke]

I can't launch it, too. Same error. Maybe it just works on the original launcher.

Maybe a libPath is missing?

[jkroepke]

I resolved this issues by using the fixes from forge and modify the distributed versionManifest from mojang.

See: https://gist.github.com/jkroepke/bea657959a625c50297ceb7797df452c

Maybe this isn't straight forward, but it just works.

[panwolfram]

@jkroepke Could you please tell me how to apply this fix to creator-tools?

[jkroepke]

Do have not any knowledge about Java coding. Sorry.

[DaMatrix]

download the file as version.json and put it next to your modpack's src folder

[panwolfram]

Great! That worked perfectly!

…

On 4 Jan 2018, at 10:52, DaPorkchop_ ***@***.***> wrote: <https://user-images.githubusercontent.com/11216106/34558178-449bb5b6-f13d-11e7-8df4-17f440eb7c29.png> download the file as version.json and put it next to your modpack's src folder — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#205 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AERjXhDWH8PBC64nmSWtGV2xmutVdOP4ks5tHJ9NgaJpZM4PdPAG>.

[gailingmic]

Awesome to hear that its the error i pointed to! Maybe someone can fix it in java now :-) the forge commit should explain it good enough (would do it myself but im only good in c++)

[panwolfram]

Could anyone fix it?

[sk89q]

Is still an issue I should look into?

[panwolfram]

Yes, it's still an issue. I can't launch literally any modpack because of it.

[gailingmic]

Yes its still an issue! The forge guys had the exact same error too and managed to fix it! All you have to do is to not search for the mac natives as theyre packaged with the game already.

My post above links the forge issue wich explains it better

[jkroepke]

See #205 (comment) for the fix.