Do not begin with a reinstall. First establish a comparison that changes only one relevant condition. In this case, the account rejects fresh authenticator codes on a new phone. Try the controlled comparison before altering drivers or login details.
Symptoms and scope
Identify the purchasing account, launcher build, game install drive and the last successful sync or patch. The defining symptom: The account rejects fresh authenticator codes on a new phone. A screenshot of the actual prompt or a short local recording can be more useful than recalling the message from memory.
- What fails: The account rejects fresh authenticator codes on a new phone.
- Best comparison: Compare the device time synchronization, correct account and whether old authenticator enrollment was transferred.
- What counts as fixed: A legitimate two-step sign-in succeeds on the authorized account.
Why it happens
A launcher tracks ownership, content manifests, local downloads and user preferences separately from the game executable. Fixing the wrong layer can cause unnecessary redownloads or save conflicts. For this case, the decisive diagnostic boundary is: Check the exact failure time and token source without transmitting backup codes or secrets. This is a hypothesis to test with evidence, not proof that the named component is defective.
The order matters: Compare the device time synchronization, correct account and whether old authenticator enrollment was transferred. A different result on the comparison run narrows the search toward settings, content, account permissions or the current session. The same result in both environments suggests looking at the shared layer instead.
Before making changes
Identify the purchasing account, launcher build, game install drive and the last successful sync or patch. Save important work, capture the error text and record the current launcher, game or device version. If the fault involves progress or cloud sync, make a separate copy of user data before any replacement or reset.
Safety boundary: Never disable security via unofficial tools or send recovery codes to third parties. A test should be reversible, authorized and limited to the specific game or application. Do not disable anti-cheat, account protections, or operating-system security just to hide the message.
Step-by-Step Troubleshooting
Start with reversible tests and choose Advanced for a focused diagnosis.
Identify what still works
Reproduce once, then stop. The account rejects fresh authenticator codes on a new phone. Record the complete on-screen text, exact title/edition and when the failure begins. Identify the purchasing account, launcher build, game install drive and the last successful sync or patch. Do not keep retrying if there is an unsaved game, an active purchase or a pending upload; protect that state first.
Compare the right scenario
Run the controlled test: Compare the device time synchronization, correct account and whether old authenticator enrollment was transferred. Use the same device, version and account unless the comparison specifically requires changing one. Note the two outcomes in a simple table: baseline failed / comparison worked, or both failed. That difference tells you where to investigate next.
Apply one reversible correction
Correct the implicated layer only: Use Ubisoft's official backup codes or account recovery path and correct device time. Before clicking Confirm or Repair, check that the dialog refers to the intended game, save or user profile. Restart only the affected app where possible; do not reset unrelated account settings or reinstall every component.
Confirm the intended outcome
Retest the original trigger: A legitimate two-step sign-in succeeds on the authorized account. Repeat after closing and reopening the affected app. If the test fails, revert the one change that was made and move to the Advanced checks rather than trying random workarounds.
Capture the first failing layer
Evidence to collect: Check the exact failure time and token source without transmitting backup codes or secrets. Correlate the first failure time with the game log, launcher history or supported service status. Collect only logs the publisher permits; redact account IDs, access tokens, e-mail addresses and private chat from any diagnostic bundle.
Separate local state from service state
Layer isolation: repeat this comparison without introducing unrelated variables: Compare the device time synchronization, correct account and whether old authenticator enrollment was transferred. A result that follows one title, account, host or edition requires a different remedy from a failure that follows the entire PC or console. Note which layer changes before modifying the configuration.
Repair the proven cause, not everything
Scoped remediation: Use Ubisoft's official backup codes or account recovery path and correct device time. Use official launcher verification, built-in account settings or supported application repair, depending on the evidence. If a previous test was inconclusive, leave protected files and firmware untouched and seek the software vendor's documented path.
Validate and prepare escalation evidence
Technical acceptance test: A legitimate two-step sign-in succeeds on the authorized account. Compare a new run with the recorded baseline and note the changed variable. If still failing, document the game build, timestamps, exact error and results of this test: Compare the device time synchronization, correct account and whether old authenticator enrollment was transferred. Never disable security via unofficial tools or send recovery codes to third parties.
Common mistakes to avoid
Destroying useful evidence: avoid wiping caches, save folders or profiles before recording the state. Never disable security via unofficial tools or send recovery codes to third parties. Use the narrowest supported correction and retest the original action.
Misreading the fix: Use Ubisoft's official backup codes or account recovery path and correct device time. This is an appropriate action only when the comparison points to the relevant layer. If the service is unavailable or the feature is not supported for the account, changing local files cannot supply missing eligibility.
How to verify the fix
Pass condition: A legitimate two-step sign-in succeeds on the authorized account. Repeat the same action at least twice, including one fresh launch, reconnect or session transition. Confirm that the change does not break another mode that previously worked.
Keep a concise before-and-after record: game or application version, affected mode or server, the one setting changed, and whether the outcome persists. An improvement in a different mode does not count as passing the original test.
Solution Checklist
If the problem continues
Return the test setting to its original state if it did not help. Then use the next evidence-based investigation: Check the exact failure time and token source without transmitting backup codes or secrets. If the result indicates publisher service, account entitlement or competitive eligibility, contact the authorized support or server administrator with the exact error and timestamps.
Keep private account identifiers, email addresses, payment records, invite links and logs containing tokens out of public tickets. Provide redacted screenshots instead. Never disable security via unofficial tools or send recovery codes to third parties.
Prevent recurrence
Keep a record of the last working game build and supported settings for this feature. After a major patch, driver update or account change, rerun the small comparison before changing several settings at once: Compare the device time synchronization, correct account and whether old authenticator enrollment was transferred. This is especially useful when a failure occurs only in one game mode.