Skip to main content
When a title chooses to use the Simplifed User Model, a game can call XUserAddAsync with the AddDefaultUserSilently option and are guaranteed to receive a valid user. Once you have the user, you can fetch their gamertag and indicate who is control of the game. If the title is not using the Simplified User Model, there is no guarantee that there will be a default user at launch. Games can choose whether or not to try and find that default user calling XUserAddAsync with either the AddDefaultUserSilently or AddDefaultUserAllowingUI options. If these return E_GAMEUSER_NO_DEFAULT_USER, the title will need to have an initial interactive screen where they ask for a user to sign-in. When the user chooses to engage, likely by clicking on the game-provided button, the title can call XUserAddAsync without the default options. This will show UI and allow the title to get a user for the game.

​
See Also

Opting into Default User Required XUserAddAsync
Last modified on August 4, 2026

Related topics

UsersChanging the Default User for the GameTroubleshooting Sign-in and Sandbox ErrorsXR-112 Establishing a user and controller on activationUser identity and XUser APIs in the GDK