Here’s what ChatGPT thinks to know about this… Bad news, I’m afraid…
”This issue isn’t a simple bug — it’s a long-standing architectural limitation between the Nintendo SDK and Bedrock’s Xbox Live integro ation layer. On Switch, only one active Microsoft account session is allowed per console process. Player 1’s profile locks the authentication channel; all other local players are treated as offline guests.
Mojang can’t open multiple concurrent Xbox Live sockets, because the Nintendo Network SDK exposes a single shared connection handle to the game process. The Xbox Live client inside Bedrock can’t re-authenticate for player 2+ without violating Nintendo’s sandbox rules. That’s why the PlayStation version behaves identically: both platforms restrict external network logins to one per game instance.
The result is that every local co-op player beyond Player 1 loses their Microsoft-linked data (skins, realms sync, achievements, owned packs). It’s been repeatedly closed as duplicate of MCPE-58640 since 2019, with no public clarification.”
Guillaume Duveau
Here’s what ChatGPT thinks to know about this… Bad news, I’m afraid…
”This issue isn’t a simple bug — it’s a long-standing architectural limitation between the Nintendo SDK and Bedrock’s Xbox Live integro ation layer.
On Switch, only one active Microsoft account session is allowed per console process. Player 1’s profile locks the authentication channel; all other local players are treated as offline guests.
Mojang can’t open multiple concurrent Xbox Live sockets, because the Nintendo Network SDK exposes a single shared connection handle to the game process. The Xbox Live client inside Bedrock can’t re-authenticate for player 2+ without violating Nintendo’s sandbox rules.
That’s why the PlayStation version behaves identically: both platforms restrict external network logins to one per game instance.
The result is that every local co-op player beyond Player 1 loses their Microsoft-linked data (skins, realms sync, achievements, owned packs). It’s been repeatedly closed as duplicate of MCPE-58640 since 2019, with no public clarification.”