[MCL-13419] Launcher would not start on OSx

When clicked on in Finder the Minecraft would just jump once and exit without any message.

When run from console it just prints this and terminates:

$ /Applications/Minecraft.app/Contents/MacOS/launcher 
2020-03-21 15:26:06.525 launcher[95049:7428971] Claimed it found a path: /Applications/Minecraft.app/Contents/MacOS/launcher (/Applications/Minecraft.app/Contents/MacOS/launcher) 4096
https://launchermeta.mojang.com/v1/products/launcher/022631aeac4a9addbce8e0503dce662152dc198d/mac-os.json
SaveToBuffer failed

$ java -version
java version "1.8.0_152"
Java(TM) SE Runtime Environment (build 1.8.0_152-b16)
Java HotSpot(TM) 64-Bit Server VM (build 25.152-b16, mixed mode)

I tried to remove and re-copy the bundle to Applications multiple times, I tried with multiple users on the same machine. I am looking for any clues on how to find out what's the problem.

This is Mojave 10.14.6.

Linked issues

duplicates 1

MCL-14985 Windows Minecraft Launcher DNS Resolve Issues Resolved

is duplicated by 1

MCL-13486 Minecraft Launcher cannot log in Resolved

Attachments

launcher_log.txt

Comments 4

migrated 2020-03-25T20:18:17Z

I tried to remove all javas (I had multiple versions), then I installed oracle 11.6 jdk using binary intaller, but the problem is still the same.

$ ls -lah /Library/Java/JavaVirtualMachines
total 0
drwxr-xr-x  2 root  wheel    64B Mar 25 21:11 .
drwxr-xr-x  4 root  wheel   128B Sep 21  2018 ..

$ java --version
No Java runtime present, requesting install.

# Installed it here

$ java --version
java 11.0.6 2020-01-14 LTS
Java(TM) SE Runtime Environment 18.9 (build 11.0.6+8-LTS)
Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.6+8-LTS, mixed mode)

$ ls -lah /Library/Java/JavaVirtualMachines
total 0
drwxr-xr-x  3 root  wheel    96B Mar 25 21:12 .
drwxr-xr-x  4 root  wheel   128B Mar 25 21:12 ..
drwxr-xr-x  3 root  wheel    96B Mar 25 21:12 jdk-11.0.6.jdk

$ /Applications/Minecraft.app/Contents/MacOS/launcher
2020-03-25 21:16:35.383 launcher[1464:75212] Claimed it found a path: /Applications/Minecraft.app/Contents/MacOS/launcher (/Applications/Minecraft.app/Contents/MacOS/launcher) 4096
https://launchermeta.mojang.com/v1/products/launcher/022631aeac4a9addbce8e0503dce662152dc198d/mac-os.json
SaveToBuffer failed

Any more advice?

migrated 2020-03-28T10:52:21Z

I solved this problem by reinstalling java and minecraft-Launcher.

migrated 2020-03-28T15:24:17Z

I was able to work around the problem by adding

13.32.120.139 launchermeta.mojang.com
13.32.120.139 launcher.mojang.com

into /etc/hosts. Ping and all other services are able to do dns lookups correctly, so not sure why the Minecraft launcher can't.

How I found the workaround:

With the help of dtruss tool, I was able to find the launcher_log.txt (pity that noone pointed me to it - it's in /Users/[your_username]/Library/Application Support/minecraft/launcher_log.txt.

In the

[media]

I noticed

[Error: 2020-03-28 15:06:48.572628: NetQueue.cpp(444)] NetQueue: No ip address available. Error code 6, Url: launchermeta.mojang.com
[Info: 2020-03-28 15:06:48.572777: NetQueue.cpp(480)] NetQueue: Action failed with result "Could not resolve: launchermeta.mojang.com (Could not contact DNS servers)" (6) :

not sure why it does not work, as I was able to happily ping the address. I added the address to my /etc/hosts. After that the launcher tried to download bunch of files and crashed later. New log file nativeUpdaterLog.txt appeared in the same dir and according to it it failed to lookup the launcher.mojang.com. So I added that to /etc/hosts as well. After that the launcher started succesfully into login screen. I tried to remove the hosts entries then and it was still starting (but per log it was still failing to resolve the names). Only when I removed the /Users/[your_username]/Library/Application Support/minecraft it was failing again.

migrated 2021-01-08T13:35:14Z

Hi, I am happy you resolved the issue. Be careful with your change however, as in the future if we ever change the IP address of our services, you could be running in to connection issues again.