[MCL-21498] Minecraft 1.19 Pre-release 2 not available from launcher

Running the latest version of the launcher, I have no access to the second prerelease of Java Edition 1.19. I can only access the first prerelease. Checking the patch notes tab also fails to show the second prerelease's patch notes. I've attached screenshots showing where I would expect to see mentions of the Prerelease.

Linked issues

is duplicated by 2

MCL-21505 1.19 Pre-release 2 does not show up in Minecraft Installations Resolved

MCL-21541 latest snapshot is still prerelease 1 but there are newer snapshots Resolved

Attachments

launcher_logs.tar.gz

Comments 17

[MOD] Greymagic27 2022-05-23T19:45:07Z

I saw a case of this over in Discord as well I believe.

migrated 2022-05-24T04:24:33Z

Doing a little more digging, I saw that the launcher seemingly always has these lines in it:

[Info: 2022-05-24 03:45:45.633017314: NetQueue.cpp(632)] NetQueue: Starting net action [https://piston-meta.mojang.com/mc/game/version_manifest_v2.json?_t=2022-05-24T03:45:45Z]
[Info: 2022-05-24 03:45:45.778468774: NetQueue.cpp(551)] NetQueue: Action finished: https://piston-meta.mojang.com/mc/game/version_manifest_v2.json?_t=2022-05-24T03:45:45Z
[Info: 2022-05-24 03:45:45.778474965: NetQueue.cpp(579)] NetQueue: Action finalized: https://piston-meta.mojang.com/mc/game/version_manifest_v2.json?_t=2022-05-24T03:45:45Z
[Info: 2022-05-24 03:45:45.778508499: GameVersionManager.cpp(432)] Got available versions manifest from https://piston-meta.mojang.com/mc/game/version_manifest_v2.json?_t=2022-05-24T03:45:45Z

That is, it requests the version manifest from this URL and gets it. I noticed it will do this regardless of whether or not the json file already exists, which makes sense. Checking the URL myself (though with the timestamp removed) shows that pre-release 2 doesn't show up there either. Firefox's Page Info window claims it was last modified May 18, 2022 at 11:16:32 MDT (aka 17:16:32 UTC).

So it seems like the issue is with this URL not being updated. Either the JSON file needs to be fixed, or there's a new URL and my launcher won't update to a version that knows this. (I only bring up the second possibility because I feel like I'd see more complaints online if everybody was getting an outdated JSON file.)

[MCQA] Zgajak 2022-05-24T07:42:48Z

Hi there!

Have you tried reinstalling the Launcher?
Have you tried deleting .minecraft (copying it elsewhere beforehand)?
Could you also please try to boot Launcher in beta mode?

This ticket will automatically reopen after you reply.

migrated 2022-05-24T08:32:31Z

I am using the latest version of the "Other" archive for Linux distributions to launch the launcher. I haven't tried the beta version of the launcher, but moving the ~/.minecraft directory leads to some weird results.

The very first launch (where ~/.minecraft doesn't exist), 1.19-pre2 shows up exactly as you'd expect. (The screenshot first_launch.png shows this.) The second launch, however, claims that 1.19-pre1 is the latest snapshot, even though it still knows about 1.19-pre2. (See second_launch.png)

While looking at each instance's launcher_log.txt, I noticed that the first time launch loads from a different URL:

[Info: 2022-05-24 08:05:41.641070772: NetQueue.cpp(632)] NetQueue: Starting net action https://launchermeta.mojang.com/mc/game/version_manifest_v2.json?_t=2022-05-24T08:05:41Z
[Info: 2022-05-24 08:05:41.867565882: NetQueue.cpp(551)] NetQueue: Action finished: https://launchermeta.mojang.com/mc/game/version_manifest_v2.json?_t=2022-05-24T08:05:41Z
[Info: 2022-05-24 08:05:41.867574699: NetQueue.cpp(579)] NetQueue: Action finalized: https://launchermeta.mojang.com/mc/game/version_manifest_v2.json?_t=2022-05-24T08:05:41Z
[Info: 2022-05-24 08:05:41.867615506: GameVersionManager.cpp(432)] Got available versions manifest from https://launchermeta.mojang.com/mc/game/version_manifest_v2.json?_t=2022-05-24T08:05:41Z

Notice that the url points to the launchermeta subdomain instead of piston-meta. (The second launch of the launcher goes for piston-meta, same as my normal ~/.minecraft directory does.)

I don't know why, but it seems that https://launchermeta.mojang.com/mc/game/version_manifest_v2.json has the correct contents, while https://piston-meta.mojang.com/mc/game/version_manifest_v2.json does not. I also don't know why the launcher picks different URLs depending on whether it's a fresh launch. The strange occurrence in second_launch.png can be explained by the fact that the ~/.minecraft/versions/1.19-pre2 is still there for the launcher to parse, but ~/.minecraft/versions/version_manifest_v2.json gets overwritten with the incorrect piston-meta file.

I've kept copies of the ~/.minecraft directory as it appeared after the first and second launches, if you need more info to poke at.

[media]

[MCQA] Zgajak 2022-05-24T09:02:41Z

Hi again!

I cannot reproduce this issue,
Could you please upload a full launcher_log file, for both the first launch and the second?
Also, is there anything out of ordinary that you do with Launcher? Anything that might help me reproduce this issue?

This ticket will automatically reopen after you reply.

7 more comments

migrated 2022-05-24T10:03:47Z

The way I use the launcher is by downloading https://launcher.mojang.com/download/Minecraft.tar.gz and unpacking it. Every time I want to use the launcher, I go into the unpacked directory through a terminal and type

./minecraft-launcher

and then it just goes from there. I don't pass any args or modify any configuration by hand. I use this tarball because I'm on a Gentoo system, so neither of the other Linux options would make sense for me.

I've attached a tarball with both logs named for easy identification. I also included a unified diff of a version of the logs with the timestamps removed, in case that would make it easier to compare them. (Just to be clear, the provided log files themselves do not have these timestamps stripped.)

If you haven't already, I suggest checking the piston-meta URL I mentioned earlier; on my end the latest snapshot version (found under the "latest" key) claims the latest snapshot is 1.19-pre1, and there's no 1.19-pre2 information anywhere in it. I've checked the URL on multiple devices, so I can safely rule out my computer randomly deciding to cache this URL somewhere in the operating system. If it looks as expected for you then there must be something really weird going on with how I connect to the address. (And again, the launchermeta version of the link is exactly what I would've expected.)

[media]

migrated 2022-05-25T13:08:30Z

With the release of 1.19-pre3 I can confirm that the launcher still doesn't show anything beyond 1.19-pre1. https://piston-meta.mojang.com/mc/game/version_manifest_v2.json is now two versions behind https://launchermeta.mojang.com/mc/game/version_manifest_v2.json . Unfortunately I see no way of forcing the launcher to download from the up-to-date url every time, so either an update to the launcher or to the piston-meta version of the manifest would be necessary.

I don't know if it's all that relevant, but while looking I noticed that the checksums and timestamps for every 1.19 snapshot differs between the two manifests. Every over version of the game is identical between the two. That gives me the sense that something changed about the release process heading into 1.19, and perhaps that same thing has now caused piston-meta to no longer be updated.

[MCQA] Zgajak 2022-05-25T13:49:15Z

Hi once more!

Few last questions, do you have some antivirus installed? Or maybe any of the incompatible software ?
Also do you have the latest version of JDK java installed (18)?

I would like to ask you to write step by step what you are doing in this form:

Steps to Reproduce:

Observed Results:

(Briefly describe what happens)

Expected Results:

(Briefly describe what should happen)

This ticket will automatically reopen after you reply.

migrated 2022-05-25T14:25:16Z

No antivirus or incompatible software.

I don't have JDK 18 installed, but I don't see how that would matter since Minecraft (to my knowledge) still runs on 17. I just let the launcher use its own downloaded JDK, I've never bothered trying to get it to use anything already installed.

Steps to Reproduce

Be someone who has run the launcher at least once before (that is, a ~/.minecraft directory exists and has the usual contents)
Download the "OTHER" tarball for Minecraft on Linux (https://launcher.mojang.com/download/Minecraft.tar.gz) to make sure you have the very latest executable.
In a terminal, go to wherever you downloaded the tarball.
tar -xvzf Minecraft.tar.gz
cd minecraft-launcher
./minecraft-launcher

Observed Results:

The "latest snapshot" option for Minecraft Java Edition lists "1.19-pre1", and going into the "create new installation" screen won't let you make a 1.19-pre2 or 1.19-pre3 installation. Unless you've gotten those two versions' JSON files and placed them manually, the launcher won't know about 1.19-pre2 or 1.19-pre3 because it's not in the version manifest.

Expected Results:

The two versions in question are readily available, and the built-in "latest snapshot" installation is currently set to "1.19-pre3".

To be honest, I really struggle to see how this could be a problem on my end. It seems pretty obvious that the problem is that a JSON file on Mojang's website is now, for some reason, not being updated. Unless https://piston-meta.mojang.com/mc/game/version_manifest_v2.json contains 1.19-pre2 and 1.19-pre3 when other people look at it, it really seems it must be a problem on Mojang's side. If necessary I can upload a copy of the version manifest as I see it from this URL.

migrated 2022-05-26T11:27:06Z

I decided out of the blue to open up the launcher because I felt like playing pre3, and when I checked piston-meta in Firefox, I saw it was still outdated. However, booting up the launcher gave me exactly what I'm supposed to get: an up-to-date version manifest! Checking the manifest confirms it's the launchermeta one, and the logs show that now most (if not all) requests for a piston-meta link get met with a request to try a launchermeta URL instead, which the launcher listens to.

So now I have an updated manifest, and updated 1.19 snapshot JSON files too (likely due to the previously-mentioned checksum differences). I've kept a copy of the log from this good run just in case, but it seems to me like the issue has been resolved now.

migrated 2022-05-26T19:10:46Z

I am still having this issue as well, running Windows. I downloaded the launcher for the first time about a week ago. The Latest Snapshot is 1.19-pre1 for me.
here's what I've tried--

Repairing the MC launcher
Removing, then reinstalling the minecraft launcher

Checking & Unchecking the Snapshot box

Clearing cached account tokens

Clearing the Game Directory, Java Executable, and JVM arguments fields
Opting out of, then back into, then back out of the beta launcher.

I'm about at my wits end here-- I don't know how to update version_manifest_v2 or other things that are being discussed above.

migrated 2022-05-27T07:21:24Z

Just booted up the launcher again, and the manifest is broken once more. It seems my launcher didn't get the memo to try launchermeta instead this time, which just makes me wonder why it worked that one time. So now it's only pulling from the outdated piston-meta link. I've tried booting up the launcher a few times, and it didn't do the right thing any of those times.

migrated 2022-05-30T18:08:22Z

Still stuck on 1.19-pre1, despite Pre-release 4 being out now. I did finally get around to trying out the beta launcher (2.3.200), just in case, and I get the exact same (broken) behavior.

migrated 2022-05-31T15:32:44Z

Yet another confirmation. Only pre1 shows up, and nothing after that. I am on Windows. I have changed nothing between these versions. The launcher broke on its own, for no apparent reason.

[MOD] Greymagic27 2022-06-01T21:30:33Z

Can you confirm if this is still an issue or what snapshots are currently being affected?

migrated 2022-06-02T08:25:01Z

I can also confirm that the launcher now shows the "latest snapshot" to be what I expect, thanks to the piston-meta URL being up-to-date now. So from my end at least, the problem has been solved.

[MCQA] Zgajak 2022-06-02T09:04:19Z

Closing the ticket as Fixed.