I thought I’d just raise this as a very big oversight, as im going through this issue with my son’s account currently.
When the authenticator was a standalone app a few years back, if by chance we upgraded our phones or reset them, we could enter the serial and restore codes for that authenticator to regain access.
Now with the app’s merged, the app redirects to the website for login which requests a push notification or code from the authenticator app, which is now locked inside the app.
Why was this ability removed when the apps were merged? This creates a loop that is only fixable through a full recovery of a user’s account. Would it not be better to have the restore function for the authenticator available before login?? or some other way to restore the authenticator without logging into the app fully?
What does it show when you access the Serial & Restore Codes menu in the App? Is that where it is asking for you to login to the website?
I’d love to know where you found that app, the current Android version i have doesn’t have that feature. v1.25.0.31 release date 29.05.25
Id post a photo, but im not allowed to sorry.
imgur[dot]com [forward slash] a/tJJnDeL
Posting your screenshot for visual reference.
It must be differences between the Android & the iOS versions of the app. I’m on an iPhone so using the iOS version.
Are those symbols at the bottom ( 
) just part of your phone OR are they part of the app?
They are just part of the Android Phone. back/home/list of apps.
That said, I also have an iPhone, and I have the same login screen as you.
Edit- after a bit of playing around and removing the app from my phone and re-installing it. The authenticator option isn’t there until you log in on your phone for the first time. After that, it appears.
The problem they’re having, and one that sadly you can’t really get past in the merged app, is that you can get to the point you show in your screenshots, but no further. There is literally no way I’ve found to update a serial/restore code. None. That is what is nissing from the app. Rather crucial when changing to a new device. I just tried this by wiping my Battle.net app and data from my tablet (it’s still on my phone), and you absolutely cannot get to any point where you are given the option to enter the serial/restore codes.
@OP: Regarding the login loop - try setting your default browser to Chrome if it isn’t currently the default. Firefox will result in an endless loop when trying to log in. It’s a bug players have known about for over two years now and remains unresolved. You can change your default browser back to your preferred app after you complete the login sequence.
If you are able to, log into your account preferrences here on the website and click Security > Battle.net Authenticator > Get Restore Code. Choose SMS if you have to since you can’t access the authenticator proper just yet. Make sure you’re logged in and at the point the app is allowing you to access the authenticator section as seen in Kyzera’s post. Choose the enter code manually option if presented with that and then have the website send the SMS restore code.
To post links type or paste the URL into the editor window here and while the URL is highlighted in full, click the </> icon at the top of the editor window to create a url like this: https://imgur.com/a/tJJnDeL
The bigger problem here is that there is zero facility to enter a restore code to put the authenticator on a new device or a backup device anymore like you could with the old standalone authenticator app. Trust me, almost nobody likes the Battle.net mobile app.
Edit: Even though I can’t enter a restore code, it appears that as long as I have the original functioning authenticator from my phone the tablet authenticator matches the rolling TOTP code properly, despite the tablet’s “restore” code being different than my phone. The app is just terribly designed and leaves even veteran users confused.
Also, want to note that the best location for feedback regarding the mobile app will be the Forum linked below.