I understand the problem, I even mention it within the description. It doesn't mean that the frequent outage isn't a bug that needs to be fixed. It can be a mojang server-side bug causing the frequent outages. Or inadequate capacity, that would also be a defect.
It could also be viewed as a bug that the client doesn't cache the skins it successfully got in the past when it is unable to connect to the skin server.
I'm not reporting that the service is down. I'm reporting that it's a bug that the service is frequently down, and that the client doesn't handle the outage gracefully. (I would classify gracefully as using previously found skins)
I also have this problem, and with the latest launcher 2.0.834 (macOS).
I've noticed that the authentication token seem to remain OK so long as I don't change what network I'm connected to. However, as soon as I change my network, the token becomes invalid. This is very frustrating, as I travel all the time, continually changing networks.
Since only the reporter is able to update the Affected Versions, could someone from the Mojang team update the Affected Versions based upon the comments that others have made?
MC-23![[Mojang] Jeb (Jens Bergensten)](../../../data/assets/gravatar/jeb.jpeg){kind=small}
I understand the problem, I even mention it within the description. It doesn't mean that the frequent outage isn't a bug that needs to be fixed. It can be a mojang server-side bug causing the frequent outages. Or inadequate capacity, that would also be a defect.
Apologies. Please direct me to the bug tracking system for the skin server. I'll open the ticket there.
It could also be viewed as a bug that the client doesn't cache the skins it successfully got in the past when it is unable to connect to the skin server.
I'm not reporting that the service is down. I'm reporting that it's a bug that the service is frequently down, and that the client doesn't handle the outage gracefully. (I would classify gracefully as using previously found skins)
Yes, both riding rails, and throwing ender pearls make this problem much more noticeable.
If the problem occurs in the future, what is the best way to get the debug information back to Mojang?
I also have this problem, and with the latest launcher 2.0.834 (macOS).
I've noticed that the authentication token seem to remain OK so long as I don't change what network I'm connected to. However, as soon as I change my network, the token becomes invalid. This is very frustrating, as I travel all the time, continually changing networks.
On version 2.0.1004 now. Still an issue.
This is seriously frustrating.
Since only the reporter is able to update the Affected Versions, could someone from the Mojang team update the Affected Versions based upon the comments that others have made?