thaledeganites

Navin Gidwani how did you overcome that issue? My workaround isn't working for me anymore!

Also, here are my launcher logs from before and after manually changing the version number. The first one looks about the same as everyone else's, failing to update launcher-core-ado and then shutting down.

I found a workaround that doesn't require going offline.

Head to Application Support > minecraft > launcher and look for a hidden file called .version (if hidden files are not visible, press cmd + shift + . to show them).

Open .version with TextEdit and change the number shown to the most recent version of launcher-core-ado. In my case, this meant changing the number from 2.2.12147 to 2.3.240, though anyone reading this in the future will probably need a different number.

You can determine that number by checking launcher_log.txt after failing to open the launcher. Look for the error, and then check a couple lines above it for a message from LauncherConfiguration.cpp that says "We should change launcher-core-ado from version number x to version number y." Version number y in that line is what you need to write into your .version file.

This stops the launcher from checking for updates, and now it runs properly every time. I guess it also leaves you running an un-updated launcher, but that doesn't seem to be causing any problems for me. The game launches just fine. I imagine you'll have to edit .version again once there's a new update.