Navin Gidwani
- navisnav
- JIRAUSER701640
- Europe/Stockholm
- Yes
- No
MCL-20784Added Attachments:
launcher_log-2.txt
Removed Attachments:
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.
Hello there! I am here to say that my Minecraft Launcher has been bugged the same way others' launchers have been bugged in this issue. My Minecraft Launcher recently had a launcher update and I needed to log in, I tried logging into Microsoft, although it said "Something went wrong in the login process." I then tried to log into Mojang, and it worked although when I logged in, it put me into demo mode. Now this bug actually happened to me on September 27 or 28 of this year and was fixed for me on September 30. Hopefully the same thing happens where it is fixed in a short amount of time! I am on a mac OS 10.11.6. I hope Mojang notices this issue and fixes the launcher for all players. For people who are reading this comment and also encountering the issue, you can use any client for now such as Badlion or Lunar Client although it would be nice to have the actual Minecraft launcher back so that we get more versions to play.
Hey guys! Just something happened to me and that is that the Minecraft Launcher just recently had another update, although it does not fix the problem unfortunately. Just thought I'd point this out!
Edit: I just got word that there is a new and improved Minecraft Launcher for Windows 10 & 11. The launcher has something to do with the Xbox game pass and is found in the Microsoft Store. For a while now though, some people on Mac have been having issues with logging into Microsoft with recent Minecraft Launcher updates, hopefully this will be fixed soon.
Hello CM! I'm just curious, what did you press after hitting the button "Add account?" Because when I press MICROSOFT LOGIN, it still says "Something went wrong in the login process." If I login with my Mojang Account, it would work, but it would say "PLAY DEMO" and would advertise me to buy the full game which I already did before.
Hello everyone! For all the new people who have reported this issue (since I have said this before), you can use Lunar Client/Badlion Client or any other client of Minecraft while waiting for the Minecraft Launcher to get fixed. It works on Mac OSX 10.11.6 and should also work for people on Windows/Linux. You can use any client BUT I would recommend using either Lunar or Badlion Client since they are very well known in the Minecraft community and are very easy to work with! You can just watch tutorials on YouTube on how to work with them and how to download it! Thanks!
@Patty Snider, most of everyone is on Mac OS (specifically 10.11.6), but there are also some people on Windows 7 (if im not mistaken) and Linux Debian 10 (buster). I'm not too sure if there are any other versions of Linux or Windows that have the problem.
Thanks @Donuts1000,
Just like @Mike Ordoñez said, I think this will calm down all of our nerves since we were all worried that we wouldn't get this problem fixed at all.
Hey guys! I got an update for the Minecraft Launcher (I'm on Mac OS 10.11.6) but unfortunately, it still did not work. Although, it is great to see that it is truly being worked on!
Thank You, @Donuts1000. It's truly been nearly 4 weeks since this problem happened. We ALL appreciate you and the Mojang team and staff for fixing this issue for Mac users. We all apologize if we were impatient and hopeless about this issue. Thank you!
I'm not too sure if this should be put here but when the launcher is fixed which is great, although, I can't launch any of the recent 1.18 snapshots and it says "Game Crashed, An unexpected issue occurred and the game has crashed. We're sorry for the inconvenience. Exit Code: 0." I can launch other versions such as 1.17, 1.16 and lower. I'm on Mac 10.11.6.
Hello! I get a message whenever I try to launch 1.18-pre2 - 1.18 (official version); "An unexpected issue occurred and the game has crashed. We're sorry for the inconvenience. Exit Code: 0." The reason why I find this 'bug' very weird is because I can launch snapshots 21w37a until 1.18-pre1. The launcher log I attatched is my launcher log after trying to launch 1.18. launcher_log.txt
Hopefully this can get fixed soon.
Hello!
I'm not too sure if this is a bug. I'm fairly positive that this is because Mac 10.11.6 is too low of a version. 1.18 pre2 and above run on Java 17 and people on mac 10.11.6 currently cannot get java 17 and only java 16 causing them to only be able to play until 1.18 pre1. Hopefully MAYBE java 17 can be on mac 10.11.6 but we'll have to wait and see.
Hey! I have been having this issue for quite a while now. To be fair, I thought it was just me who was having this issue. Luckily, I'm most likely getting a new laptop before my school starts, but I would still like to play as I'm very impatient. I tried deleting every minecraft file I had, and re-downloading the launcher via the website. There was a thing I noticed though every time I tried downloading it. Whenever I'd download, the launcher would say "updating" every time. I would be able to open the launcher ONCE, then if I close it, then reopen it, it wouldn't work. I'm on a mac OS version 10.11.6. I'm also not a tech guy but I noticed that in my files, even when I downloaded it today, the date it says that I downloaded it says "March 24, 2022, 7:04 AM."
thaledeganites, i need a bit of help. I read your recent message saying I need to change this number to that number in .versions. Well, i checked my launcher_log.txt and the number I need is 2.3.280 but, I already changed the number, saved the textedit file, tried re opening the launcher and it still closed. So i re checked the launcher log, and now it said "We should change launcher core-ado from 2.3.280 to 2.3.280" so now I am SO CONFUSED. what should i do?
Nevermind! I have accomplished the work. Lets go! Thanks so much!
thaledeganites, I'm not too sure. Yesterday, once I closed the minecraft launcher, the glitch happened again where it wouldn't open, so I just re-did the same steps and it worked once again!