[MCL-16425] An invalid checksum error appears in the launcher log when downloading a new version

The bug

When I downloaded and launched 1.16.5 Release Candidate 1 for the first time, the following error was printed in the launcher log. (However, the corresponding game log in the minecraft/logs folder did not contain any mention of this error.)

Download from https://launchermeta.mojang.com/v1/packages/3a5d110a6ab102c7083bae4296d2de4b8fcf92eb/1.16.json had invalid checksum! Expected: 3a5d110a6ab102c7083bae4296d2de4b8fcf92eb got: 7a46ac95adabfc3b83cfe5c12d7ee291b133e6a2

Despite this error, the game still launched normally. As requested in this comment from MCL-13885, I will upload 1.16.json and version_manifest_v2.json to this report.

Files

[media]

Linked issues

is duplicated by 2

MC-220206 Download Bug Resolved

MCL-16669 Invalid Checksum Error Resolved

relates to 1

MCL-13885 Invalid Checksum When Launching Default Minecraft Launcher Resolved

Attachments

version_manifest_v2.json

version_manifest_v2-1.json

version_manifest_v2-2.json

version_manifest_v2-3.json

version_manifest_v2-4.json

Comments 19

pine1needle 2021-01-15T22:33:15Z

Interestingly, I did not get any errors when I downloaded and launched the 1.16.5 full release today.

migrated 2021-01-19T10:50:30Z

Yes we are also a bit confused why this happens 🙂
We are working on improving error handling around checksum issues which should provide us with more information on why this happens

pine1needle 2021-01-20T16:27:56Z

This happened again when I downloaded 21w03a for the first time.

Download from https://launchermeta.mojang.com/v1/packages/13b4faf35c0ae2a672a6c60fcbee91b215852810/1.17.json had invalid checksum! Expected: 13b4faf35c0ae2a672a6c60fcbee91b215852810 got: 07df9d665e93595da3daf9ee0607e5e0700152e0

Files

[media]

(version_manifest_v2.json was automatically renamed to version_manifest_v2-1.json by Jira because a file with the same name was already attached to this report.)

[Mod] markderickson 2021-01-20T17:10:55Z

I can confirm that this is an issue with the 21w03a download. The same error is presented to me.

j_p_smith 2021-01-20T17:13:53Z

Can confirm; I received the same error in my launcher log upon upgrading to 21w03a.

GameCallbacks.cpp(162)] Launcher/launcher (main) Error Download from https://launchermeta.mojang.com/v1/packages/13b4faf35c0ae2a672a6c60fcbee91b215852810/1.17.json had invalid checksum! Expected: 13b4faf35c0ae2a672a6c60fcbee91b215852810 got: 07df9d665e93595da3daf9ee0607e5e0700152e0

9 more comments

pine1needle 2021-02-03T22:41:27Z

This happened again today, when I downloaded 21w05a for the first time.

Download from https://launchermeta.mojang.com/v1/packages/0085c15a6318aa2d235ee553f70c22284b43bf7b/1.17.json had invalid checksum! Expected: 0085c15a6318aa2d235ee553f70c22284b43bf7b got: 15c6ff15f8c8e73f3983b0d6a9779dc607dd698a

Files

[media]

(These files will be renamed by Jira again because attachments on this report have the same names already.)

pine1needle 2021-02-04T21:58:34Z

Today when I downloaded 21w05b for the first time, a warning was printed instead of the usual error.

Local file /Users/REDACTED/Library/Application Support/minecraft/assets/indexes/1.17.json has wrong SHA-1 hash, expected ff71ef080ad9ef91f661a9f5ba9ece6b8a6ea719 but was 0085c15a6318aa2d235ee553f70c22284b43bf7b

This warning included my real-life name, so I replaced it with "REDACTED" above.

Files

[media]

(Jira automatically renamed the attachments again.)

pine1needle 2021-02-11T00:09:23Z

This happened again when I downloaded 21w06a for the first time. This report already has many attachments, so from now on I will only post a comment with the warning (without 1.17.json or version_manifest_v2.json). (If it would be better for me to continue posting these files, then please post a comment to tell me.)

Local file /Users/REDACTED/Library/Application Support/minecraft/assets/indexes/1.17.json has wrong SHA-1 hash, expected 358623ca0695a0e1180013039011b77bfc03d6d8 but was ff71ef080ad9ef91f661a9f5ba9ece6b8a6ea719

pine1needle 2021-02-18T05:16:57Z

The warning was printed again; this time it was for 21w07a.

Local file /Users/REDACTED/Library/Application Support/minecraft/assets/indexes/1.17.json has wrong SHA-1 hash, expected d76d2ae366af6820990b10bb149b3360a41a59d2 but was 358623ca0695a0e1180013039011b77bfc03d6d8

I've noticed that below the warning, there are info lines printed in the launcher log that say the file with the wrong hash was deleted and then redownloaded. Additionally, the "wrong" hash in these warnings is the same as the "expected" hash from the previous time the warning was printed. To me, this implies that the file was not downloaded with an incorrect hash; it is just outdated (as is expected). In contrast, when errors used to be printed instead of warnings, the "got" hash did not match the "expected" hash from the last time the error was printed. ~~Since these warnings seem to behave in a much more sane way than the errors used to behave, I believe~~ ~~this report should be resolved as fixed~~.

pine1needle 2021-02-26T01:59:48Z

Today I downloaded 21w08b for the first time and an error was printed in the launcher log instead of a warning. Perhaps this is because I skipped 21w08a?

Download from https://launchermeta.mojang.com/v1/packages/0305fa3b64cb3e7c32cab0d3458eb4d948ebf18f/1.17.json had invalid checksum! Expected: 0305fa3b64cb3e7c32cab0d3458eb4d948ebf18f got: 403c05265c769085a6c63ce2d2f3471fb006093c

Files

[media]

pine1needle 2021-03-10T21:59:14Z

For 21w10a, it went back to printing a warning instead of an error.

Local file /Users/REDACTED/Library/Application Support/minecraft/assets/indexes/1.17.json has wrong SHA-1 hash, expected b762b22ffe62ae5302ff175cde96f575bd09b53e but was 0305fa3b64cb3e7c32cab0d3458eb4d948ebf18f

Are these comments still useful or is it becoming overkill?

migrated 2021-03-11T12:22:01Z

Haha thanks mate, your comments have been good. Obviously there is a common theme with this issue and new releases of snapshots. You don't need to add these comments anymore 🙂

[Mod] markderickson 2022-02-02T17:08:39Z

I couldn't reproduce this issue when downloading version 22w05a. Is this still an issue for you?

pine1needle 2022-02-03T01:23:41Z

When I downloaded 22w05a, a warning was printed in the log:

Local file /Users/REDACTED/Library/Application Support/minecraft/assets/indexes/1.18.json has wrong SHA-1 hash, expected 40b267e61ee41d3fc403c0c0addd24ada34c28f6 but was 77ed3c6d51997991b61b8e5a80688602a816115a

The warning was followed by two "info" log entries:

Deleted Local file /Users/REDACTED/Library/Application Support/minecraft/assets/indexes/1.18.json

Downloaded https://launchermeta.mojang.com/v1/packages/40b267e61ee41d3fc403c0c0addd24ada34c28f6/1.18.json to /Users/REDACTED/Library/Application Support/minecraft/assets/indexes/1.18.json

After Minecraft finished launching, I also manually verified that the hash of 1.18.json was 40b267e61ee41d3fc403c0c0addd24ada34c28f6 by using Terminal.

Receiving these log messages when a new version is downloaded seems rational to me (like I mentioned a while back). So if the messages are always these ones instead of the error messages, then maybe this report should be resolved as fixed? (However, apparently I also previously speculated that the errors might now only occur when you skip a snapshot, so perhaps that should be tested first?)

migrated 2022-02-07T11:49:37Z

Hi there!
Could you provide us with more in-depth repro steps?
Does this issue still occurs to you on newest version of Launcher?
Have you tried to install Launcher from the minecraft.net website?
Do you use VPN or any of the incompatible software on machine you try to log-in?

This ticket will automatically reopen when you reply.

pine1needle 2022-02-17T05:16:12Z

I skipped 22w06a and now I have downloaded 22w07a. It printed a warning instead of an error:

Local file /Users/REDACTED/Library/Application Support/minecraft/assets/indexes/1.18.json has wrong SHA-1 hash, expected cb628cc0e2e76461209692e4d74b5c6fdd0fab9e but was 40b267e61ee41d3fc403c0c0addd24ada34c28f6

That was followed by two "info" log entries like before.

Then I created a new installation for 22w06a and downloaded that version for the first time. No warning or error was printed; only a single "info" message was printed:

Downloaded https://launcher.mojang.com/v1/objects/b863174b1147a6a9d9ab4922d9ced4eee19452ac/client.jar to /Users/REDACTED/Library/Application Support/minecraft/versions/22w06a/22w06a.jar

Since the errors seems to no longer occur, this report should probably be resolved as either "Fixed" or "Cannot Reproduce".

My current launcher version is 2.2.10324, but I'm not sure which version was the first version that no longer printed errors when downloading a new snapshot.

pine1needle 2022-02-17T05:26:45Z

Given my above comment, I'm not sure if these answers are still relevant, but I'll answer @unknown's questions anyway.

When the errors used to be printed, the only repro steps were to ensure the "Open output log when Minecraft: Java Edition starts" option was enabled in the launcher settings, and then launch a version of Minecraft that you had not already launched previously.
Unlike when this report was initially created, the launcher now only prints warnings, not errors. (See my above comment.)
When I installed the launcher, I did install it from minecraft.net. I have not tried re-installing the launcher.
I do not use a VPN or any similar software when logging-in.

migrated 2022-04-06T15:24:52Z

Closing the ticket as per comment of the reporter @unknown.

pine1needle 2022-04-20T22:08:59Z

@unknown messaged me on the Mojira Discord saying that he was able to reproduce this in 22w16a. I checked my log when downloading 22w16a and I also had an error printed in it.

Download from https://launchermeta.mojang.com/v1/packages/13dd8d9c2b9e49437718d9151754cf764febac62/1.19.json had invalid checksum! Expected: 13dd8d9c2b9e49437718d9151754cf764febac62 got: 8aba36a8541cf5218315ed6adfa678faabd07aa5

I'm not sure why it was printing warnings before and is now printing errors again.