[WEB-8] Some users have multiple UUID records for agent:minecraft

Several users have multiple UUIDs, documented here is one user "jumbokiller2001".

{"name":"jumbokiller2001","agent":"minecraft"}

{"id":"e01c28e44f2443389440e07974a47393","name":"JUMBOKILLER2001"}
{"id":"6d0409ceb40c4580b2075e19d6a12003","name":"JUMBOKILLER2001"}
{"id":"a8e27c733217448ab7166ae32f00799c","name":"JUMBOKILLER2001"}
{"id":"a5d19e7fb70f4a7ab9bfaf02eda2562a","name":"JUMBOKILLER2001"}
{"id":"311a4cacf4584766aa89212a55d9ea3d","name":"JUMBOKILLER2001"}

Code used:
A very simple wrapper created from https://github.com/Mojang/AccountsClient

String name = "jumbokiller2001";
Profile[] profiles = profileRepository.findProfilesByCriteria(new ProfileCriteria(name, "minecraft"));
        if (profiles.length == 1) {
            return profiles[0].getId();
        } else {
            for(Profile profile : profiles) {
                System.err.println(gson.toJson(profile));
            }
            return "Couldn't get the UUID! :(";
        }

Linked issues

relates to 1

WEB-11 Demo accounts are returned by the API Resolved

Comments 49

Ben Smith 2014-03-21T02:32:06Z

Whoever formatted this for me, you're a saint, thankyou.

kumasasa 2014-03-21T06:32:49Z

Tip: Embrace code sections with {code} tags.

Ezekiel 2014-03-21T15:41:08Z

I can verify this on my UUID converter

Array
(
    [profiles] => Array
        (
            [0] => Array
                (
                    [id] => e01c28e44f2443389440e07974a47393
                    [name] => JUMBOKILLER2001
                )

            [1] => Array
                (
                    [id] => 6d0409ceb40c4580b2075e19d6a12003
                    [name] => JUMBOKILLER2001
                )

            [2] => Array
                (
                    [id] => a8e27c733217448ab7166ae32f00799c
                    [name] => JUMBOKILLER2001
                )

            [3] => Array
                (
                    [id] => a5d19e7fb70f4a7ab9bfaf02eda2562a
                    [name] => JUMBOKILLER2001
                )

            [4] => Array
                (
                    [id] => 311a4cacf4584766aa89212a55d9ea3d
                    [name] => JUMBOKILLER2001
                )

        )

    [size] => 5
)

Dito Windyaksa 2014-03-21T16:00:43Z

Also, Fishbans api can't search the UUID of this user.

http://api.fishbans.com/stats/JUMBOKILLER2001

{"success":false,"error":"Unable to get UUID for this user."}

Anon Ymus 2014-03-23T13:31:36Z

Confirmed.

39 more comments

AgentK 2014-03-26T11:46:53Z

Out of the 3.1mil users in our DB, these are the ones affected (outputted from an implementation of the Mojang AccountsClient):

[2014-03-26 06:38:01] [INFO] UUID Migrator booting up.
[2014-03-26 06:38:03] [ERROR] Multiple records found for tww1400: 578d5a93f88f41fa8f0c300028b0e25a, 61ce21daa0bb4f5a9ace82d27ce88f13, f9dc1522847c4a078fafe89f170789c5, e6c9e6e1583842c7bc8c8205be3f6609
[2014-03-26 06:38:03] [ERROR] Multiple records found for chicken_cream: 0e5962a9fd7a4f2d90b1b8d9d324dd9b, caf5e547413b4496a2673446eaf852b1
[2014-03-26 06:38:04] [ERROR] Multiple records found for kill3rben: 600b6e9c32574ac48725a9d4d337f498, df2439d6ae3f4f58b0e51ce5c1be8d51
[2014-03-26 06:38:05] [ERROR] Multiple records found for voilled: 44581a559ea04bcd802e0ac336ac9fe2, cad7f3b38e3340b8ab657863cb92a6cd
[2014-03-26 06:38:07] [ERROR] Multiple records found for majcake: 19969dac06c24476860fa765d36f2f8e, 13c692c042644943a906fedae7301e1a
[2014-03-26 06:38:07] [ERROR] Multiple records found for goldenapple1018: 9fe4bb3d02b747eca0c5599bae0e0978, f48afa83983c48ad98988c4dd142282d
[2014-03-26 06:38:07] [ERROR] Multiple records found for lou2ag: dea969ea0bc648f290c8e3015363e532, 5f3d710623e64e14bd32523e2c29c311, 2293f4ab7787418994003a0d513619f9
[2014-03-26 06:38:09] [ERROR] Multiple records found for greasyspic: e83a017992474db2862e61edc69e6b45, 8b377f6a36f74ea4893f467d4c7600d7
[2014-03-26 06:38:14] [ERROR] Multiple records found for taken8: 677b6f913c8d4612a361457f1155ae61, 829ab5c045e448df96b94b965f1775b8
[2014-03-26 06:38:14] [ERROR] Multiple records found for ash_9000: ea927f99e48544618247150c7088d7e1, 86abc5fdf1344d05843b965d5b468fdf, 7ae2f8e9be224329a85a84374fe3d303, 5c13bc3c1a3342c88d1c1a7b4000cfb5, 8bea3ff12e554a06970b0a4f0cae2ff6
[2014-03-26 06:38:14] [ERROR] Multiple records found for wjrmaxhd: a7c3cb8b925b4957916ff1f0a0c92ce9, 676522ca7b9541acaea9adaa837a82c8, 5e9b62a3f88e438abbdc39a0d9853da3
[2014-03-26 06:38:17] [ERROR] Multiple records found for panthinol: fdd4303509654498bb6a9b74ab840d34, 0765f8c063ed487381214ccbafcfe162
[2014-03-26 06:38:17] [ERROR] Multiple records found for giraffe310: a33bae2e28544507b2afebc617cc5e38, bcd6de2d93af400b9ad8255ca1f5c8f6
[2014-03-26 06:38:23] [ERROR] Multiple records found for baconlover4ever: 40ad6e8b1dbf4699a93810ba5e12257f, b6fee3a423694c04b734ce3c0f29ede3, 30fc7f53cc584dfb89f72dad1101889d
[2014-03-26 06:38:23] [ERROR] Multiple records found for xchewiex: fa0e96225497403fa3824b3c3baf93f9, 06bc3ca57717481fba9d7abbb840440a
[2014-03-26 06:38:28] [ERROR] Multiple records found for jumbokiller2001: e01c28e44f2443389440e07974a47393, 6d0409ceb40c4580b2075e19d6a12003, a8e27c733217448ab7166ae32f00799c, a5d19e7fb70f4a7ab9bfaf02eda2562a, 311a4cacf4584766aa89212a55d9ea3d
[2014-03-26 06:38:35] [ERROR] Multiple records found for nico: 3bfb7c8d02a24ece8b56c7e22a553be3, 24107f5e4e4c49d0b25f423d0a9fc337

Nathan Adams 2014-04-01T09:20:51Z

This is being looked into now, we found a total of ~50 users that were affected by this problem.

AgentK 2014-04-02T16:11:52Z

I can confirm that it's fixed from my end. Thanks! 🙂

MonsieurApple 2014-04-06T20:59:29Z

Is this issue really resolved? Both of the following:

https://sessionserver.mojang.com/session/minecraft/profile/e01c28e44f2443389440e07974a47393
AND
https://sessionserver.mojang.com/session/minecraft/profile/6d0409ceb40c4580b2075e19d6a12003

return data for JUMBOKILLER2001, however, only the first one has proper skin data.

Nathan Adams 2014-04-06T23:14:16Z

Yes, it is. That's a separate issue of /profile/ not caring about if an account was flagged as deleted or not 😉

MonsieurApple 2014-04-06T23:55:53Z

Awesome, thanks for the confirmation 🙂

Ezekiel 2014-04-11T13:39:31Z

To add to that, Monsieur, you wouldn't be looking up a UUID that was never sent. What matters is the username to UUID and (that same) UUID to username works properly

deleted 2014-04-13T00:22:10Z

Doesn't seem to be fixed.
user nico returns this:

{
  "profiles": [
    {
      "id": "3bfb7c8d02a24ece8b56c7e22a553be3",
      "name": "nico",
      "legacy": true,
      "demo": true
    },
    {
      "id": "24107f5e4e4c49d0b25f423d0a9fc337",
      "name": "Nico"
    }
  ],
  "size": 2
}

Please reopen.

Ezekiel 2014-04-13T00:25:54Z

Reopened & Confirmed Redstone Sheep's comment

Ben Smith 2014-04-13T00:44:59Z

http://nooooooooooooooo.com/

Matthew Horrigan 2014-04-13T01:02:37Z

Now, I am no expert, but the one name is Nico, and the other is nico.

Charles-William Crete 2014-04-13T01:06:01Z

Matthew has a point. When looking up for a name, it will return all profiles with the same name, even if not the same caps.

Anon Ymus 2014-04-13T01:10:12Z

Indeed. The profiles are also clearly separate, as one is a legacy and demo account and the other is neither.

Ben Smith 2014-04-13T01:15:13Z

Oh ok, so false alarm?

I'm unclear if this is still an issue or not.

If the intended behaviour is for the username -> uuid lookup to return a single uuid, so as far as it looks, even if it's for the demo account reasons, it's still an issue.

Joe Grimes 2014-04-13T01:21:52Z

Even if it's a false alarm, it should definitely still be looked into because although they have a different case they should technically have the same UUID as Mojang only accepts new accounts based of a different letter/number combination. Having two show up when checking a player name may become a little confusing right? I'm with Ben on this one.

Charles-William Crete 2014-04-13T01:24:45Z

It should go like so:

Display exact username's profile
Then
Display non-exact (other caps) username's profile

Ben Smith 2014-04-13T01:27:20Z

Is that an authoritative statement, or a suggestion?

deleted 2014-04-13T01:36:00Z

I don't think this is false alarm. Usernames should be unique in any capitalization.
This problem makes it very hard for automatisation. How am I supposed to figure out the correct UUID for player nico?
Requesting the UUID for a single player shouldn't return multiple ones.

As an example, a script would probably request the UUID for a user and then pick the first entry or the first entry where the username matches (case-insensitive)
In this case it would pick the legacy/demo one.

I tested this by creating a Nico.dat user and then convert it by running a newer server version. It renamed it to 3bfb7c8d-02a2-4ece-8b56-c7e22a553be3.dat, which is, as you can see "nico" and not "Nico"

Please reopen.

Ben Smith 2014-04-13T01:38:07Z

Looks like the vanilla minecraft server assigns the wrong UUID to this user.

I just ran a test startup of an online mode vanilla server and it exceptioned out (but still converted) Nico.dat to 3bfb7c8d-02a2-4ece-8b56-c7e22a553be3.dat

Bug still present in vanilla server, please mark as unresolved.

deleted 2014-04-13T01:40:30Z

Ben: you be stealing my idea much! 😃

btw: it's probably more likely to be a bug on the server side. Mojang should scan their database for duplicate names and remove them, if possible.

Ben Smith 2014-04-13T01:42:47Z

It looks like this issue can currently arise from legacy account holders/demo account holders buying accounts and this not being properly handled by the system, but obviously we don't have any idea about the internal workings, so we can only conjecture.

As far as server owners are concerned, yes, it is possible to get a wrong uuid for a user, and in fact is quite likely if you happen to get one of the users affected by this bug since it seems the incorrect uuid is the ony first in the list, which will result in (when it gets fixed) the correct uuid being the second one, which means that any server that tried to convert them beforehand will have the wrong uuid saved!

deleted 2014-04-13T01:46:43Z

No it shouldn't return multiple accounts in any favoured order. First, Mojang might probably need to create a custom JSON parser to realize this and second, it totally depends on the language/library (on the client side) which order the results have, if any at all.

Ezekiel 2014-04-13T02:12:18Z

Reopening again. Usernames are not case sensitive, and one username should never return two UUID's, even if they are technically different usernames.

Dlawso the Really Lucky Rabbit 2014-04-23T02:25:45Z

Thinking that the "Fix Version" needs to be changed to "Future Version" due to Ezekiel's post.

deleted 2014-04-23T12:38:29Z

Fix Version?
Anyway this is an API problem, that doesn't have anything to do with Minecraft (and it's versions).

Ezekiel 2014-04-23T14:48:55Z

The profile for Nico appears to be fixed.

deleted 2014-04-23T16:48:41Z

No, it still returns two accounts using https://api.mojang.com/profiles/page/1, which is what current versions use AFAIK.
Using https://api.mojang.com/profiles/minecraft will only return one account, but that's probably only because it does not return demo accounts.

Ezekiel 2014-05-01T21:34:01Z

@unknown, that method is depreciated and not valid

deleted 2014-05-01T22:04:06Z

It may be deprecated, but it's still used by very recent versions.
Since this is an API problem and not a client problem, it should be fixed on the API side.
I don't see what's not valid with that, but it still does return multiple accounts.
So the API problem originally reported still exists for that API.

Ezekiel 2014-05-02T00:05:02Z

It is strongly discouraged that you use that version, as it is only still online for compatibility reasons and should not be used by any production software.

Also, when you say

It may be deprecated, but it's still used by very recent versions.

What 'versions' are you referring to?

deleted 2014-05-02T00:18:52Z

I just tested with 1.7.8. It throw an error but converted the file anyways (with the wrong UUID!)

Conversion failed, please try again later
og: Could not convert file for Nico
	at oe.a(SourceFile:331) ~[minecraft_server.1.7.8.jar:?]
	at oe.onProfileLookupSucceeded(SourceFile:312) ~[minecraft_server.1.7.8.jar:?]
	at com.mojang.authlib.yggdrasil.YggdrasilGameProfileRepository.findProfilesByNames(YggdrasilGameProfileRepository.java:58) ~[minecraft_server.1.7.8.jar:?]
	at ny.a(SourceFile:58) ~[minecraft_server.1.7.8.jar:?]
	at ny.a(SourceFile:349) [minecraft_server.1.7.8.jar:?]
	at ls.aE(SourceFile:472) [minecraft_server.1.7.8.jar:?]
	at ls.e(SourceFile:153) [minecraft_server.1.7.8.jar:?]
	at net.minecraft.server.MinecraftServer.run(SourceFile:339) [minecraft_server.1.7.8.jar:?]
	at li.run(SourceFile:628) [minecraft_server.1.7.8.jar:?]

It works in 1.7.9, but again, that is because it uses a different API than the one reported and thus shouldn't be topic of this ticket.

Ezekiel 2014-05-02T01:43:11Z

1.7.8 is old, and it's fixed in 1.7.9

deleted 2014-05-02T01:49:03Z

"old"
However, it's not fixed in 1.7.9. It uses a different API, that's a difference.
The thing that bugs me is that it could easily be fixed for versions < 1.7.9 by just fixing the API. There surely are a lot of people using MC < 1.7.9.

Ezekiel 2014-05-02T02:50:01Z

version 1.7.5 doesn't have UUID compatibility, if I understand correctly. 1.7.6-1.7.8 were broken versions that weren't released for more than a little while. Therefor it can be assumed the usage for 1.7.6,1.7.7, and 1.7.8 are extremely low and insignificant.

deleted 2014-05-02T02:57:40Z

Okay 😉

FearThe1337 2014-05-10T14:29:11Z

While using the UUID lookup api for our player uptime tracking system I encountered a user who still has multiple uuids.
Apparently there is a uuid for 'milo00' and for 'Milo00'.
(Only difference is a different capitalization, but minecraft usernames are not case-sensitive?).
Assuming this bug has not been fully fixed yet?

Also, I seem to be having almost 200 names in my database who don't seem to have an uuid at all?

Ben Smith 2014-05-10T14:43:44Z

Yeah, just drop those 200 users. They're people who refunded their Minecraft purchase or were removed for other reasons.

Ezekiel 2014-05-10T19:24:59Z

@unknown, you are using a depreciated API. Please use the correct API calls in the future, to avoid broken responses.

http://github.com/Mojang/AccountsClient/wiki

FearThe1337 2014-05-10T20:10:00Z

Using the latest api (Which I was already using) the name still returns 2 different uuids for this user if the lookup has more then 1 name specified.

String[] names = new String[] {"Notch","milo00" };

HttpProfileRepository rep = new HttpProfileRepository("minecraft");
Profile[] profiles = rep.findProfilesByNames(names);

for (Profile profile : profiles) {
	System.out.println(profile.getName() + ":" + profile.getId());
}

outputs

Milo00:7e3fcc4b0f1a4c04a7f4987fa7f65185
Notch:069a79f444e94726a5befca90e38aaf5
milo00:175d2f30a0f0485e8ebc46c81ea1af5c

Same for the php code I was using

<?php
	function uuidArray($usernames){
		$json = json_encode($usernames);
		
		$ch = curl_init();
		$curlConfig = array(
			CURLOPT_URL => "https://api.mojang.com/profiles/minecraft",
			CURLOPT_POST => true,
			CURLOPT_RETURNTRANSFER => true,
			CURLOPT_POSTFIELDS => $json,
			CURLOPT_HTTPHEADER => array(
				'Content-Type: application/json',
				'Content-Length: ' . strlen($json)
			),
		);
		
		curl_setopt_array($ch, $curlConfig);
		$json = curl_exec($ch);
		curl_close($ch);

		$response = json_decode($json);
		return $response;
	}
	
	$names = array();
	$names[] = 'milo00';
	$names[] = 'Notch';
	
	print_r(uuidArray($names));
?>

which yielded the output:

Array
(
[0] => stdClass Object
(
[id] => 7e3fcc4b0f1a4c04a7f4987fa7f65185
[name] => Milo00
)
[1] => stdClass Object
(
[id] => 069a79f444e94726a5befca90e38aaf5
[name] => Notch
)
[2] => stdClass Object
(
[id] => 175d2f30a0f0485e8ebc46c81ea1af5c
[name] => milo00
[legacy] => 1
[demo] => 1
)
)

Ezekiel 2014-05-10T20:15:34Z

Reopened, issues still occur when there are two names in a request

deleted 2014-05-10T21:13:36Z

The new API is now returning demo accounts, too.
Thus we got the same problem again. For some reason it only returns two accounts (e.g. Nico/nico) when more than 1 user is requested.

Ben Smith 2014-05-10T22:27:55Z

How very strange, well caught!

Ezekiel 2014-05-11T02:41:43Z

I noticed that earlier today as well

[Mojang] Kristoffer Jelbring 2014-05-12T08:26:47Z

The public API has now been updated to exclude demo profiles from the listing (which is the intended behavior). Thanks for bringing this to our attention!