Workaround:
1. Download a fresh copy from Minecraft.net and install (keep prior copy, new one is noted with (2).
2. Go offline
3. Launch (new) Minecraft app offline (it will offer to let you play offline or retry)
4. Go back online, wait a bit and then click play, play offline or retry ...depending if it recognizes you are online.
5. Play Minecraft!
- launching the app offline bypasses the auto update process. Thankfully, the current version has not been updated with the apparent bug. I grabbed a few copies in case I accidentally update.
Problem persists. We now have 3 computers with same issue. We are locked out. New logs today:
I just downloaded a fresh copy of Minecraft (from minecraft.net). It updated bootstrap and then crashed, same as old copy. The logs look to be exactly the same as ones uploaded earlier today ...so I won't upload new ones. Rebooting didn't help either.
Lots of other reports coming in for this (or similar) launcher issue: MCL-15564, 21235, 21275. I am running Mac OS 10.11.6 but I see other platforms and OS's affected. Please at least revert the update that caused this. Thank you.
Same problem on Mac.
This bug just happened today upon yet another launcher update. Yesterday it worked fine.
I think the clue to the problem is: "Unable to load nib file: NativeUpdater, exiting". Terminal doesn't record this specific action when the launcher is healthy.
I have tried quitting/restarting launcher and rebooting computer ...but no luck solving the issue. I have two computers now with same problem.
As of today, I have this same launcher problem on my mac. Launcher does nothing after "bootstrap" update. Pasted below is text from Terminal generated during crash:
Last login: Thu Apr 21 15:00:26 on ttys000
PBNJ-MacPro-6:~ pbnj$ /Applications/Minecraft\ 2.app/Contents/MacOS/launcher ; exit;
2022-04-21 15:14:38.567 launcher[69294:8323074] Claimed it found a path: /Applications/Minecraft 2.app/Contents/MacOS/launcher (/Applications/Minecraft 2.app/Contents/MacOS/launcher) 4096
2022-04-21 15:14:39.089 nativeUpdater[69295:8323086] Unable to load nib file: NativeUpdater, exiting
logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.
[Process completed]
In a duplicate report MC-242661, Mojang has confirmed the problem to be a compatibility issue with Java 17 and Mac OS 10.11 or older. The report was closed and marked as "resolved". They stated that we can still play older versions which is true however not on Realms. I would like to suggest that Mojang allow older versions on Realms.
We can play older versions, yes ...but not on Realms with friends and family. I had to cancel my Realms account and move my worlds to a 3rd party server (Minehut). So, by cutting off Mac OS 10.11 users, there will be a drop in Realms accounts unless you let us play non-current versions (which is currently not allowed). Our computers are working perfectly; they just can't be updated.
Can we please have an update on this bug/issue? It's been over 2 months now. If Microsoft is dropping support for Mac OS 10.11.6, it would be fair to let us know and to update the Minecraft system requirements to reflect this change. There is a great number of unresolved reports on this bug and thousands of unhappy campers in the online forums. It would be great if Mojang could confirm or correct our suspicions so we can move forward. To make things worse, those of us who play with our families on Realms can no longer access our 1.17 worlds because Realms doesn't allow older versions of the game. Perhaps this policy can be examined? Regardless, the Minecraft fans deserve to be updated. Thank you.
Can we please have an update on this bug/issue? If Microsoft is dropping support for Mac OS 10.11.6, it would be fair to let us know and to update the Minecraft system requirements to reflect this change. There is a great number of unresolved reports on this bug and thousands of unhappy campers in the online forums. It would be great if Mojang could confirm or correct our suspicions so we can move forward. To make things worse, those of us who play with our families on Realms can no longer access our 1.17 worlds because Realms doesn't allow older versions of the game. Perhaps this policy can be examined? Regardless, the Minecraft fans deserve to be updated. Thank you.
Can we please have an update on this bug/issue? If Microsoft is dropping support for Mac OS 10.11.6, it would be fair to let us know and to update the Minecraft system requirements to reflect this change. There is a great number of unresolved reports on this bug and thousands of unhappy campers in the online forums. It would be great if Mojang could confirm or correct our suspicions so we can move forward. To make things worse, those of us who play with our families on Realms can no longer access our 1.17 worlds because Realms doesn't allow older versions of the game. Perhaps this policy can be examined? Regardless, the Minecraft fans deserve to be updated. Thank you.
Can we please have an update on this bug/issue? If Microsoft is dropping support for Mac OS 10.11.6, it would be fair to let us know and to update the Minecraft system requirements to reflect this change. There is a great number of unresolved reports on this bug and thousands of unhappy campers in the online forums. It would be great if Mojang could confirm or correct our suspicions so we can move forward. To make things worse, those of us who play with our families on Realms can no longer access our 1.17 worlds because Realms doesn't allow older versions of the game. Perhaps this policy can be examined? Regardless, the Minecraft fans deserve to be updated. Thank you.
@Mojang the "Affects Versions" is noted as (macOS - 10.9 only) but most of the reports here are using 10.11.6. If I didn't add this before, my mac (10.11.6) is using Java 8.
@@unknown
Are we sure that OS 10.11.6 can't update to Java 17? ...and have you confirmed that Minecraft 1.18 must use Java 17? Thanks, this would be helpful to know.
Thank you @Eugenio Scalfi.
I would like to add another fact.... If I switch the game back to 1.17.1, there are no errors and the game opens normally.
Unfortunately, this doesn't help me enjoy Minecraft since I play on Realms with my son and Realms doesn't allow any other versions except the newest.
When I open 1.18, it crashes like everybody elses here ...but I don't have the Java crash message.
I am on Mac 10.11.6 with Java 8.
I would also like to know if Mojang is working on a fix or not.