Some Uplay users are reporting that Google Authenticator is giving them the wrong codes every time, and so they are unable to log into the service and play their favorite games. Others tried to resolve the issue by syncing the Google Authenticator app with UPlay, but this procedure also requires them to use the 2-step authenticator method.
What is causing the Uplay Google Authenticator not working?
We investigated this particular issue by looking at various user reports and the repair strategies that are commonly being used to fix this problem. As it turns out, there are multiple potential culprits that are known to trigger this particular issue:
- Authenticator code is typed with spaces – Even though the generated code is displayed with one space after the first three letters inside the Google Authenticator app, uPlay will reject the code if it contains any spaces. If you were previously copy-pasting the code, you will be able to resolve the issue by deleting the space between the first and the last 3 letters.
- Time correction for codes is out of sync – One popular culprit that might make uPlay to reject the codes generated by Google Authenticator is time correction. Typically, if the user travels between multiple time zones, time correction might become out of sync inside the Google Authentication app. If this scenario is applicable, you can resolve the issue by syncing the time correction for code via the Google Authentication settings.
- Date & time is incorrect on the mobile device – Google Authenticator is known to generate faulty codes in instances where the time & date and the timezone are incorrect in relation to the region. Several users encountering this issue have managed to resolve the issue by setting the correct values and restarting the device.
- UPlay internal glitch – Two-factor implementation on uPlay was extremely buggy at first and it still is to some degree. In a lot of cases where users were still unable to access their account after following the most common fixes, the only fix was to open a support ticket to Ubisoft’s desk. The good news is their help agents are fast and are known to resolve the issue very quickly.
If you’re currently struggling to resolve the same problem, this article will provide you with several potential repair strategies. Down below, you’ll find a collection of methods that other users in a similar scenario have successfully used to get past this particular issue. All of the methods featured below are confirmed to be working by at least one user.
Since the methods below are ordered by difficulty and efficiency, we advise you to follow them in the order that they are presented. One of them should eventually resolve the issue regardless of the culprit that is causing it.
Method 1: Typing the Google Authenticator Code without spaces
Keep in mind that although the code generated in Google Authenticator typically contains 3 numbers, space and then another 3 numbers, you need to ignore the space as it’s only there to provide more clarity. Several affected users that we’re encountering this issue have reported that the issue was no longer occurring once they typed the Google Authenticator code without spaces.
Most applications will validate a code that contains spaces if it’s correct, but uPlay is an exception. If you were previously typing the codes with space (or you were just copy-pasting it), try removing the space and see if the issue is resolved.
If the same problem is still occurring, move down to the next method below.
Method 2: Syncing the time correction for codes
By far, the most popular fixing method for this particular issue is to open the Google Authenticator app and Syncing the Time Correction for codes. The vast majority of users that previously encountered login issues with Google Authenticator have reported that the issue has been resolved after performing these steps.
Here’s a quick guide on syncing the time correction for codes in Google Authenticator:
Note: The steps of performing time correction on the Google Authenticator app are the same whether you’re using Android or iOS.
- On your mobile device, open the Google Authenticator app.
- Inside the Google Authenticator app, click the action button (three-dot icon) in the top-right section of the screen and tap on Settings from the menu.
- Inside the Settings screen, tap on Time correction for codes.
- Once you get inside the Time correction for codes tab, tap on Sync now and wait for the process to complete.
- Try to complete the two-factor authentication process once again and see if the issue has been resolved.
If you’re still unable to play your games on Uplay because the Google Authenticator codes are incorrect, move down to the next method below.
Method 3: Setting the correct time and date on the mobile device
Other affected users have reported that the issue was resolved for them after adjusting their mobile device time and date to the correct values (in relation to their region) and restarting the device. After doing so, the codes generated by Google Two Factor Authentication worked flawlessly and they were able to play their favorite games.
Here’s a quick guide on setting the correct time on Android devices:
- From your home screen, tap on the Settings app.
- Once you’re inside the Settings app, scroll down to the System option and tap on it.
- When you’re inside the System app, tap on Date & Time.
- From the Date & Time menu, make sure that the toggles associated with Automatic date & time and Automatic time zone are enabled.
- Once you’ve done this, restart your device and check if the issue has been resolved at the next device startup.
Note: If you’re using iOS, you need to go to Settings > General > Date & time and set it to Automatic. Then, go to Settings > Privacy > Location Services and set it to Always use for Google Authenticator app.
If the codes that the Google Authenticator generates are still wrong, move down to the next method below.
Method 4: Opening a support ticket
If the methods above didn’t allow you to resolve the issue and you’re still unable to get past the 2-factor verification method conventionally, you’ll likely need to get assistance in order to fix this problem and continue playing your favorite games.
Several users that encountered the same issue have reported that they finally got a resolution on this issue by visiting Ubi’s support desk and opening a support case on the issue. You can do this by visiting this link (here).
Most users that have resolved the issue by taking this route reported that their ticket was resolved in under 48 hours.