mojira.dev

Scott Redinger

Assigned

No issues.

Reported

No issues.

Comments

I would also like to know if Mojang is working on a fix or not. 

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:

[media][media][media]

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.

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

https://launchermeta.mojang.com/v1/products/launcher/022631aeac4a9addbce8e0503dce662152dc198d/mac-os.json

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]

 

[@[Mojang] Adrian Östergård|https://bugs.mojang.com/secure/ViewProfile.jspa?name=nighter]

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.

Same issue as [MC-20783] and [MC-20784]. Not sure which string to follow.

Minecraft 1.18 crashes after clicking "PLAY" on launcher. I'm on Mac OS 10.11.6. "Error: Game crashed. An unexpected issue occurred and the game has crashed. We're sorry for the inconvenience. Exit Code: 0" 

Minecraft 1.18 crashes after clicking "PLAY" on launcher. I'm on Mac OS 10.11.6. Very disappointing start for the exciting new update ...and after waiting 4 weeks prior for the Launcher bug to be fixed. "Error: Game crashed. An unexpected issue occurred and the game has crashed. We're sorry for the inconvenience. Exit Code: 0"

 

 

Thank you Mojang!!! We are GO for 10.11.6 again. 

For those of us playing with friends/family through Realms, I suggest contacting Minecraft Help Center for Realms support and asking for a credit/refund for Oct/Nov due to this bug:  https://help.minecraft.net/hc/en-us/requests/new?ticket_form_id=360001225811 

FYI... I tried using Time Machine (Mac 10.11.6) to restore Minecraft (a copy) to before the update but it did not work. I even had turned off auto-updates before the experiment. Not sure why this did not work... I thought the non-updated launcher would have opened the game. Maybe provides some clues. If anyone has tips about doing this, please share. Maybe I did something wrong ...or perhaps the old launcher no longer works with OS.

This ticket has been open for almost a month now. It is not assigned and is noted as "postponed". The OS versions noted as affected are not accurate (OS 10.11.6 is not even listed and it is the most commonly affected). All duplicate tickets are noted as resolved. I'm guessing there are thousands of people who can't log in. I suggest that we all open new tickets, stating our operating systems. Maybe that will get us an accurate ticket ...or at least some attention. If not, I'm guessing Microsoft will soon discontinue support for Mac OS 10.11.6 and older ...and we will need to seek alternative launchers. 

Some are suggesting a work-around... to click on "add account" and then enter your existing account details. This does not work for me on my Mac 10.11.6. The website doesn't let me enter an existing account into the 'add account' interface. Dead end.