Troubleshooting
XBPlayer sign-in problems: Microsoft errors and repeated prompts
Check Microsoft account access and where sign-in stops: the confirmation page or XBPlayer. Test one attempt at a time and compare networks without resetting data.
On this page
If XBPlayer on Android will not let you sign in or keeps asking you to authenticate again, first check the same Microsoft account in a browser and note the stage where the error occurs. Then make one fresh attempt from XBPlayer. There is no need to start by clearing data, reinstalling or changing your password.
Identify where sign-in stops
Keep the error message and note the last successful step. For troubleshooting, distinguish these three situations:
| What happens | Where to start |
|---|---|
| Microsoft rejects the sign-in or requires an additional check | Check account access on Microsoft’s website and follow the instructions in the message. |
| Microsoft confirms sign-in, but XBPlayer stays on the sign-in screen | Check whether that same attempt finishes in the app. Note whether you used a code or QR code on another device. |
| XBPlayer was working but has asked you to sign in again | Record when the request appeared and what has changed since the last successful session. |
XBPlayer sign-in goes through Microsoft. We do not receive your password, and authentication tokens remain in the device’s secure storage. See the XBPlayer privacy policy for details.
Check your Microsoft account in a browser
- On the device where you confirm sign-in, open the official Microsoft account website and check access with the same account. If the site is already signed in as another user, select the correct account first.
- If sign-in fails, follow the error message: for example, complete identity verification or recover a forgotten password. For an unclear error, use the Microsoft sign-in helper. Until this check succeeds, do not keep repeating the same cycle in XBPlayer.
- If you have access, check the Xbox profile: on a shared device, you may accidentally confirm someone else’s account. See the account and profile check guide for details.
If Microsoft reports blocked cookies, check permissions for the sign-in page using your browser’s help. Microsoft explicitly states that this service needs cookies. Do not disable all browser protection or clear all saved data to address one error.
Check the date and time on Android and, if you are signing in on another device, on that device too. Correct any obvious mismatch. Also open the Xbox status page: if a sign-in outage is reported, wait until it is resolved. Successful access to Microsoft’s website narrows the search, but does not yet confirm that sign-in will complete in XBPlayer.
Complete one attempt in XBPlayer
Start a new attempt from the app and complete only that one. Do not approve several old tabs or codes at once: this makes it harder to tell which request a result belongs to.
- Signing in with a code or QR code on another device. Use the code or QR code from the current attempt, confirm the correct account on Microsoft’s page, then check the screen of the device running XBPlayer. A browser on another phone returning to an app is not the measure of success here: what matters is whether sign-in completed in the client itself. If the page says the code has expired, start a new attempt from XBPlayer.
- Microsoft’s page opened on the same Android device. Complete the confirmation and see what happens next. If the browser reports success but the app does not appear, return to the already-open XBPlayer and check its state. Note whether it is still waiting, shows an error or asks you to sign in again.
Check for XBPlayer updates in your official installation channel. If a separate browser was involved, check for its updates too. Then try signing in once more. Button names and how the page opens may vary; troubleshooting does not require guessing a menu path or changing the system’s link handler.
Distinguish a new request from an endless loop
If the request appeared after a period of normal operation, sign in once and check whether the result persists. Note whether the account, password, network or app version has changed. A single repeated request does not establish the cause.
If the app immediately asks you to sign in again, record the full cycle: starting from XBPlayer, confirming with Microsoft, and the client screen after confirmation. Once the same result repeats, move on to comparing networks or contacting support. Repeatedly entering a password without new observations does not help troubleshooting.
Compare networks without resetting settings
Run a short sign-in test on another available network, such as mobile data instead of home Wi-Fi. Keep the same device and account; there is no need to launch a game for this check. If you confirm sign-in on another device, note which network each device uses and change the connection on only one at a time.
If you use a VPN or network filter, compare results with and without it separately, where your network’s rules permit this. Restore the original setting afterward. A changed result shows a connection dependency, but does not by itself prove which component caused the error.
Leave clearing data and reinstalling for a justified next step with support: these can delete local settings and require another sign-in. Before resetting anything, keep a description of the error and clarify which data can be restored.
Send support a reproducible sequence
If sign-in still does not complete, contact our team at hi@hetko.eu. Include the details you have:
- Device model, Android version and XBPlayer version.
- Error time with its time zone and the exact message.
- Sign-in method: on the same device or with a code/QR code on another one; the name and version of any browser involved.
- The result of signing in on Microsoft’s website and the XBPlayer screen after confirmation.
- The networks you compared, whether a VPN was active, and the result of each attempt.
In screenshots, hide email addresses, codes, QR codes and the full page address containing authentication parameters. Do not send passwords or tokens. If sign-in succeeds but the game will not launch, use Remote Play troubleshooting or the cloud launch checks, depending on the mode you selected.
Sources and further reading
- XBPlayer — Xbox Remote Play and cloud gaming — XBPlayer sign-in through Microsoft, a code or QR code on another device, multiple accounts and contact details for our team.
- XBPlayer privacy policy — Privacy policy dated September 10, 2026: Microsoft sign-in and data handling. We do not receive the Microsoft password; tokens remain in the device’s secure storage.
- Microsoft account sign-in helper — Microsoft’s helper checks a sign-in problem using information entered by the user and suggests next steps.
- I can’t sign in to my Microsoft account — Microsoft help for unavailable sign-in, forgotten passwords and account checks.
- Microsoft: browser is set to block cookies — Microsoft’s official error page for blocked cookies. If you see this message, check permissions for the sign-in page.
- Xbox Status — Xbox service status page. Check outage notices at the time of your error.
Get the key points
Open a summary request with this article’s link. For Gemini, the request is copied — paste it into the chat.