mojira.dev
MCPE-71033

Only the primary PS4s XUID is being used, secondary users don't show connection

After upgrading to 1.14.60, we are having an issue where the secondary PS4 user in split screen users doesn't carry over their XUID. Users can swap who launched Minecraft and that person gets carried over.
The secondary user, when they sign into the PS4, they don't get show up as connecting to the server and their XUID doesn't show up. When they disconnect it lists their proper name but no XUID.

Once the user is on the server, they have all of their equipment but their name shows as Steve.

Attachments

Comments 13

The second player on the server shows no connected message. When they connect it shows their name as Steve in game.
When they disconnect their proper name shows up but their XUID does not show up.

This is different from the other post where the online-mode was set to false.
In the BDS, server.properties, online-mode=true

Same thing happens on Nintendo Switch. The account that launches Minecraft will have their name show up on a Realm they connect to. A second player will show up as Steve (in name & skin).

Is this still an issue in the latest version?

This is still a problem in March 2023.

3 more comments

I can confirm this is still an issue on PS5 with MC version 1.21.50 - the client doesn't send an XUID for the second player as previously mentioned (the game hangs). I should note it does work on Realms for whatever that's worth. Would be fantastic to get this fixed! 

I can confirm this is still an issue on Nintendo Switch too.

I can confirm this is still an issue on ps5 on 1.20.80

Disregard my previous about 1.20.80. I wasn’t paying attention to updates. This is still an issue for ps5 on 1.21.72.

It seems that in recent versions (1.21.131), at least on switch, the data being sent for player 2 now uses both the name and XUID of player 1.

The data being sent for player 2 is:

{
  nbf=1766084826, 
  extraData={
    identity=redacted, 
    displayName=redacted, 
    XUID=redacted, 
    titleId=redacted,
    sandboxId=RETAIL}, 
  randomNonce=-835051032898776294, 
  iss=Mojang, 
  exp=1766171286, 
  iat=1766084886, 
  identityPublicKey=redacted
}
{
  nbf=1766084826, 
  extraData={
    identity=redacted, 
    displayName=redacted, 
    XUID=redacted, 
    titleId=redacted,
    sandboxId=RETAIL}, 
  randomNonce=-835051032898776294, 
  iss=Mojang, 
  exp=1766171286, 
  iat=1766084886, 
  identityPublicKey=redacted
}

which matches the xname and xid of the data sent for player 1 (shown below):

{
  sub=redacted, 
  ipt=PlayFab, 
  iat=1766084841, 
  mid=redacted, 
  tid=redacted, 
  pfcd=redacted, 
  cpk=redacted, 
  xid=redacted, 
  xname=redacted, 
  exp=1766099241, 
  iss=https://authorization.franchise.minecraft-services.net/, 
  aud=api://auth-minecraft-services/multiplayer
}
{
  sub=redacted, 
  ipt=PlayFab, 
  iat=1766084841, 
  mid=redacted, 
  tid=redacted, 
  pfcd=redacted, 
  cpk=redacted, 
  xid=redacted, 
  xname=redacted, 
  exp=1766099241, 
  iss=https://authorization.franchise.minecraft-services.net/, 
  aud=api://auth-minecraft-services/multiplayer
}

All of the redacted data does have values, but the notable portions are xname, xid, displayName, and XUID. The formats of data sent between player 1 and player 2 are also quite different.

Patch885959

(Unassigned)

1190590

Confirmed

PlayStation

Windows 10, PS4

1.14.60 Hotfix, 1.16.1, 1.16.20, 1.20.60, 1.21.51 Hotfix

Retrieved