This bug is a glitch in all Minecraft launcher versions since 0.7.1, where random code shows up in place of the update notes.
What I expected to happen was that the launcher would show the regular update notes that are shown when the launcher shows before.
What actually happened was that it showed random code which usually shows when trying to open one of the minecraft code files in notepad (a incorrectly decompressed gzip)
Steps to Reproduce:
1. Open the minecraft launcher
(Works at random and might just be a 1 time thing)
Linked issues
is duplicated by 17
Attachments
Comments 26
Yeah, it only shows the error when it uses the 0.71 update. Doesn't affect gameplay though.
I still have a picture of it under l.tiff.
Confirmed just happened to me.
Edit: Nothing to see in console:
Launcher 0.7 (Dev) (through bootstrap 2) started on windows...
System.getProperty('os.name') == 'Windows XP'
System.getProperty('os.version') == '5.1'
System.getProperty('os.arch') == 'x86'
System.getProperty('java.version') == '1.7.0_21'
System.getProperty('java.vendor') == 'Oracle Corporation'
Trying to log in...
Logged in successfully
Delta time to compare resources: 16292 ms
Download job 'Resources' skipped as there are no files to download
Job 'Resources' finished successfullyIt might still be a 1 time glitch for most of you, but for me it happens every time, with no strange message in the console. And the launcher is 0.7.1. Don't know why it is 0.7 for windows users.
im one of the duplicates, by the way. because it REALLY bugs me, makes me think minecraft will crash 😞
Liam: Actually, raw HTML looks like <html>, <head>, etc and is much more human readable, this is an incorrectly decompressed gzip.
Oh, pardon me for that goof up. I'll see if I can find a temporary solution to this issue (as soon as I figure out how to read Java).
Is this still a concern in the current Launcher version 1.3.9 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
Does it always do that?
I'm guessing it is some sort of a transport error thus showing you the contents of an invalid compressed response from a tumblers httpserver.