Any time I try to log into my mobile authenticator, I get “this page isn’t working” and “battlenet redirected you too many times". This has been going on since early in the week, so I don’t think it is a traffic issue. I can log into WoW.
I have deleted my cookies on but I haven’t uninstalled/reinstalled the authenticator - I don’t trust that I’ll be able to access it again if I uninstall.
I can’t use the “touch to authenticate” feature - but if that’s not working, I get nervous about what else I can’t see that is not working or suspended.
My terminology may not be exact between the apps. I know that the older authenticator was retired. I don’t think I’m talking about that one.
When I tap on my mobile’s battlenet icon, it asks me to log in. I put in my information. It tries to authenticate and I get an error saying that I’ve redirected too many times. As far as I can tell, this is inside the mobile battlenet app.
If so, are you by chance using a browser other than Chrome as your default?
If you answered yes to both of those questions, you need to temporarily set your default browser to Chrome, launch the Battle.net app and log in while Chrome is your default browser. There is a known issue with other browsers (especially Firefox) on Android that causes the Battle.net app to not work right, with redirects being the primary culprit.
Once you’ve successfully logged in and can utilize the authenticator portion of the app you may reset your default browser to whatever you were using before. You’ll need to repeat these steps if your Battle.net app ever loses its tokenization, has its cache/data cleared, or is installed on a new Android device. Should you want to install on a new device you can do so without removing the authenticator from your account by logging into the Battle.net app on the new device and using the original device’s Battle.net app to approve the authentication request, which will then also tokenize the new app while leaving the original app also tokenized (allowing you to have the app on both devices at once like I do with my phone and tablet).
I am on an android device. I am using Chrome - not another browser.
It sounds like my battlenet app has lost it’s tokenization. I cleared my cache/data after several days of the problem existing, so I don’t think that caused it (but it sounds like it may be a new problem - yay!).
You’re saying I can install on a new device - is that just if I am adding an additional device (ie, having the android and the new device) or is that if I am switching from old device to new device (ie, retiring an older device)?
I appreciate the help and the information. Thank you.
Clearing the data/cache will definitely wipe the tokenization on that device. It’s the equivalent of forcing the app to behave as if it had just been installed for the first time ever. One of Android’s failings is the lack of a built in preferences/data backup feature and how it hides those items by default so that the only way (outside of Samsung’s US devices) to truly back up your device, especially piecemeal, is to root the device first and use a more powerful third party backup app or use the ADB functionality to do the same (that’s complicated and even I don’t like using that option).
Both. If you have a working Battle.net app that is properly tokenized and has a functioning authenticator activated, you can install the Battle.net app on a second / new device, launch the app and log in there, and when you do so it will cause the original Battle.net app to ask you to authorize a new login. When you accept the new login the Battle.net app on the second device will be granted its own token and will then also serve as a functioning authenticator.
The serial number and restore code on the second device will be different from the original authenticator’s SN/R codes, but since the means to enter those codes is gone in the Battle.net app that makes the codes nothing more than a visual anomaly so to speak. I’ve had two Battle.net apps working for a while now, one on my Samsung 22 Ultra phone and the other on my Samsung Galaxy S9 tablet. Either app can grant an authentication request via push notification as they are both tokenized. It isn’t tied to a phone number, but the original SN/R token itself.
This does mean that if you lose both devices or both get wiped at the same time and your account has the authenticator requirement, you’ll need to go through the process of removing the authenticator via the now required SMS Protect (that’s required now when setting up an authenticator so as to verify the phone number belongs to the account owner). As long as SMS Protect is set up and enabled, you can recover/remove an authenticator on your account, providing you have access to a device associated with the phone number your account is linked to.
To clarify the second half of your question, the newly “minted” Battle.net app on the second or new device should still function just fine as an authenticator so long as you don’t wipe either the data or cache before “minting” another Battle.net app on a different device. However, the officially recommended method for switching to a new device is to remove the authenticator from your account while you have your original device and then use the new device to create a new account association with that device via a new internal SN/R code. So long as you have access to the phone number your account is linked to, you should have no issues using either my method above or Blizzard’s own recommended procedure.