Same issue here (western Canada).
I got the same issue opening the battle.net app. I just selected to continue offline, launched wow and entered my login credentials and authenticator code. Iām now playing the game just fine. Seems like a battle.net app issue.
Doesnt work, It is asking for authenticator code and it wont take it.
Replying to confirm this works. Just launch the game offline and log in to wow directly. I was able to log onto bnet on mobile for the sake of my authenticator as well. You will need to manually generate a code.
hopefully if enough people reply here someone on forums will catch wind of this hopefullyā¦
iām still āofflineā on the app buts its letting me update my game soā¦
Yeah, it mostly appears to be a problem with the Launcher at the moment. Continuing offline and logging in on the game itself seems to still work.
It seems Blizzard is aware of this. Itās affecting me as well Area-52.
West Coast here and cant log in the normal way. I havenāt tried to do it the manual way though!
They probably have systems in place that notify them of whatās likely to be some sort of outage and donāt really need to see a forum post to be made aware of it.
Too bad I couldnāt get an advance warning though. Silly me saw a bnet update and thought nothing of it and now Iām forced into offline mode workarounds.
Midwest US hereā¦ and alasā¦ canāt log in.
having this as well right after i restarted bnet for an update. since that update unable to login.
Yup. I was able to manually log in to WOW as well.
same and the window wont go away to even try and put in my password
Yea same thing here. Was playing a couple hours ago
Edit: Was able to login through the .exe in the installation folder.
It could be a server issue but there are some suggestions in the support article: https://us.battle.net/support/en/article/65035
After that update I just did, same message.
I guess Iām not ever exiting the game!
Yeah, same thing is happening to me right now too.
Same issue. I am at least relieved to know itās a problem on Blizzās end.
Same issue here after the update.