Scott Redinger
- ScottRL
- JIRAUSER645367
- Europe/Stockholm
- Yes
- No
MCL-20407
REALMS-9995
MC-231863
WEB-5486
hello, @Scott Redinger !
Unless your computer is so old that it can barely run anything, you can easily avoid this crash by upgrading to a newer OS
The official article says that 1.18 requires MacOS version 10.14.5 or higher, so you'll need to upgrade to Monterey, Catalina, Big Sur or Mojave
However, there is a reported bug that the launcher does not start on MacOS Monterey, so the other three are better.
How to update
1, Apple logo -> about this mac
It should say the type and the year it was made. <e.g. MacBookAir (13-inch early 2015)>
2, Compare that information with this page to see if it is compatible with Big Sur
If it's not compatible with Big Sur, see this page to see if it's compatible with Catalina.
If it's not compatible with Catalina, see this page to see if it's compatible with Mojave
3, download the OS you found
download Big Sur
download Catalina
download Mojave
We have the same problem (playing on Switch). World renders painfully slow and often freezes. Have to restart the game but that doesn't fix the extreme lag. Have tried turning down render distance, turned off fancy graphics and also tried lowering resolution output to TV (1080 to 720). Problem is same when playing directly on Switch. Would like to find a solution, thanks!
Update: The bug has fixed itself however the world that was getting stuck is now gone, replaced by an older world that I had deleted prior.
Minecraft Realms crashes when trying to switch worlds and/or configure the Realm. We are using Java edition on Mac OS. Same problem on 2 different Macs.
I can't change the Realm back to my primary world. We are playing 1.17.1 and not using mods or datapacks. Issue happened after moving a new, Creative test world from Single Player to Realms ...now it is stuck, please help.
ERROR - GAME CRASHED
The game crashed whilst rendering screen
Error: java.lang.NullPointerException: Cannot invoke "java.awt.image.BufferedImage.getWidth()" because "â⁻f" is null
Exit Code: 255
update: Mojang fixed this bug with an update to the launcher. Thank you Mojang!
...
Same exact problem on two different Macs running OS 10.11.6. Launcher is no longer able to log into the new Microsoft Account (since 27.Sept 2021). After account migration it worked but then stopped (after launcher ran auto update?). Can we get an older launcher version until this is fixed? Will Minecraft/Microsoft be canceling support for older Macs? That would be terrible. My son and I are hoping for a fix soon or else we will have to cancel our subscription to Realms.
Not again, please!!! "Something went wrong with the login process." This bug is back AGAIN upon the latest launcher update. I've logged in/out numerous times, relaunched, etc... nothing fixes it. Yeah... so I'm on an older OS. 10.11.6 ...and all of our Macs have same issue. Microsoft, please.
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.
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.
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.
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
Thank you Mojang!!! We are GO for 10.11.6 again.
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" Very disappointing start for the exciting new update ...and after waiting 4 weeks prior for the Launcher bug to be fixed.
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"
The application did not create a crash report. I have uploaded the launcher log file instead. Good luck!
Minecraft 1.18 crashes after clicking "PLAY" on launcher. Mac OS 10.11.6. Launcher 1036 (1). Terminal 2.6.1 (361.1). Java 16.0.1. Launcher Log attached, last activity Dec 1. Launcher did not create a crash report.
"Error: Game crashed. An unexpected issue occurred and the game has crashed. We're sorry for the inconvenience. Exit Code: 0"
Same issue as
MCL-20783Minecraft 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"
Same issue as [MC-20783] and [MC-20784]. Not sure which string to follow.
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.
@Navin Gidwani
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.
@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.
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.
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.
@[Mojang] Adrian Östergård
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.
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.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]
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.
Same problem on Mac.
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.NativeUpdaterLog_042422
LauncherLog_042422
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.
Problem persists. We now have 3 computers with same issue. We are locked out. New logs today:
nativeUpdaterLog-3.txt
launcher_log-3.txt
latest-1.log
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.
"exit code -1" is also indicated in logs uploaded for issue MCL-21264
I would also like to know if Mojang is working on a fix or not.