However, I should also mention that like other users have experienced I am getting a Java crash window as wellas the in game crash screen error. So maybe I'm wrong about the not Java bit.
Well, I'm not sure about it being a Java 17 issue. I had previously inistalled Java 17 because I couldn't get amidst 4-7 to work on my computer and still can't but the forums for that suggested 16 which didn't work so I also tried 17 also no luck but I could still play minecraft 1.17.1. I still can play 1.17.1 but 1.18 is where I get the game crashing
Just adding a copy of my Launcher Log renamed to include my initials. I thought I had added my own copy in my previous post but when I opened the one that is linked to my comment the Username in the File path shows that it is obviously not mine but Scott Redingers.
Yeah, same for me. Mac OS X 10.11.6. Updating to 1.18 had to download about 60~ish mb. Downloading hung for ages (15- 20 mins) around 40mb. I have a good internet connection. (no, not Great but good... or good enough that this was slow) Creeped very slowly to full download. Then it had to install. Fine. This is expected. 'Finalisation' said it estimated to take about 1 minute... then hung again and I had to just wait and then crashed after about 20 mins. Exit Code: 0
I shut everything down and restarted computer. I started Launcher and got approx 50% through 'Preparing' and then crashes. Same vague error message. Exit Code: 0 after many of us have experienced vague error messages from the most recent launcher bug 19840 This is particularly frustrating. It would be good to include a more specific error message so we can report it easyier and devs can pinpoint problems. ERROR GAME CRASHED... unexpected, Exit... ZERO EXIT CODES...
This is so vague that BOTS literally turned off the ticket for a bug last time around... and probably will again with this vague crash.
Jess Edward suggested attaching the crash report for this bug with todays date... I've looked in the crash log folder... but alas todays date isn't in there. So Jess also suggests adding the launcher_log.txt, which I've attached. But I can't see anything there that points towards a crash.
In addition to this in-game or in-Launcher crash it also triggered another crash simultaniously which I couldn't screen capture via the usual method and have taken a photo of instead
Clicking on Report option brings up this report to Apple box. Probably not helpful for Apple. I doubt they care.
The contents of the 'Problem Details and System Configuration' box probably give some of you more information about my machine than I should be sharing but... to bad I'm upgrading to a different machine and OS soon anyway but want to provide some assistance to some peeps who are battling it out on some older tech like me currently... anyway... the full log is in the 'send to apple. txt' I've also attached.
This happened before... only about a month ago. I can't find where I initially reported the issue but I got some help via email or at least someone said oh try it again and 14 hours (ish) later the launcher worked again. But now the issue is back and caused by once again an unsolicited update to the launcher.
Mac OS 10.11.6
Does anyone know how I can change the tags to reflect that this is still broken?
Anthony A, I have the same result as Jonathan M L. This is not resolved. This is not fixed.
Yep, this happened to me too.
They keep on forcing an update, and then the update breaks my game. This only just happened about a month ago which is why I captured a screenshot this time.
Updated the launcher when it said the launcher would update next time it was restarted (i.e. not an optional upgrade!!!) The launcher then immediately returns the error message "Something went wrong in the login process" No further information just a failure to login.
I just had a similar problem (although I was in Java) where I would teleport and then immediately fall out of the world. If your End gateway is out over the void maybe try to create a platform several blocks below the End Gateway so you have something to land on.
Yeah, I get the same error messages. A red error message on top right of launcher tells me to restart Launcher, which I've tried numerous times now.
And also two error messages in grey.
First one says couldn't connect to Minecraft services, which I'm used to seeing if my Internet is having a bad-hair-day, so I usually just need to click Try again and it goes through the motions of checking that I have a connection.
Second grey error message says you will not be logged in automatically next session, View troubleshooting here. This link takes me through to a Linux solution for secure token issue. Shake my head. No This Is NOT The Issue. Windows 10 is my current OS. and 10.0 2.2.11696 is in my current version of Minecraft Launcher.