Remember the time when Youtube recommendations were flooded with “Among Us” gameplays? The time when close allies turn into bitter enemies; the place where Corpse Husband earned much of the internet mania? Well, the dev-team at Innersloth decided to revamp the game a bit and add a new map as well. Except that it came with a bunch of bugs and issues which might thin its player base. Here’s our take on the Among Us sign in error.
Why is “Google Auth no token” error plaguing “Among Us”?
There seems to be an impostor at work from the looks of it. Among Us has been sabotaged that players can no longer sign in to their accounts and are instead met with this message. This has happened after the recent 2021.3.31 update.
The issue isn’t restricted to any particular platform but extends across both PC and iOS/Android. “Google Auth no token” issue while logging in is not new. It is a known one. Several discussions on Twitter and Reddit are trying to salvage a possible solution.
As we mentioned earlier the issue is cross-platform so it isn’t an error with the device. Most likely a common problem which can solved with a one-for-all solution.
The latest update by Innersloth has been majorly brought about by the all-new change “Airship”. For Among Us it is probably the most ambitious by far. The map is rumored to be twice the size of Polus with unique features that are carried over from the other maps.
It offers the feature to choose the starting room as well, which might a lot more to the element of suspense. That is the biggest reason why players want the Among Us “Google Auth no token” login error to get resolved immediately.
Among Us sign in error has been reported majorly by Android players. However, iOS and PC platforms have notified login errors. The dev-team at Innersloth is working to resolving the Among Us sign in error before the player base starts losing interest. The progress on fixes and release notes are available here.
How to fix Among Us sign in error temporarily?
Well, most of the fingers are pointed at you, the player for the bug. Several players who use numerous devices with the same account or the sudden increase in the number of players are the common reasons.
The players have tried all possible means to fix the known bug of login, sign-in failure, or even create an account. These include the mandatory To Dos like clearing cache, re-installation of Among us, and even trying to login using a guest account. However, nothing seemed to work.
Since the bug is an old one, there is a tried and tested official solution. It can be given a try until a permanent fix is deployed.
Sign in to Among Us with your login credentials. You will get logged in as a guest account alternatively. In case you are still facing the same issue, log out and login in once again to the game. You are now on a guest account.
Update as on 3rd April
The devs have tweeted that the critical “Google Auth no token” issue troubling Among Us Android gamers has been resolved. The team is working on pending bugs.
Update as on 5th April
The devs have also confirmed that they are aware of the cosmetic bugs. The fix is in progress
There are however many more issues that have cropped up in the meantime worked upon by devs. Let us have a look at them.
A compilation of known issues post-“Airship” update
- Some players were facing an infinite loading screen. The issue was promptly resolved by another Redditor u/Bestsoft100. All it required was an installation of vc_redist.x86.exe
- The character sprites might be replaced with pink rectangular squares instead of the usual character models.
- The authentication error mentioned above is another one of the bugs. So, signing in will display a prompt “GoogleAuthNoToken error”. This could be due to the sudden increase in the number of players which would take a toll on the servers.
- The game currently supports only one account per game. Having the same account signed in on numerous devices can result in a sign-in error.
- Players can get stuck at one point after the Meeting. That can be resolved by opening and close the Settings menu and you should be free to move again.
The Microsoft version requires a Steam account to sign in. As a result, those who take the direct Microsoft sign-in route can be booted out and sent to the Steam store. The fix for this issue has already been made.
That’s pretty much it from our end. Do you think we’ve made note of everything? Do let us know in the comments. For more similar content visit us here.