Hey everyone,
We’ve gotten a lot of reports of this and have the developers looking into it. The info I see mentions this only happens if the Battle.net application is bypassed and the account has an authenticator attached. The workaround is to launch via the Battle.net application, using a manual code to log in, or remove the authenticator. Removing security may not be desired or advised to do, but I had to call out everything we’ve seen working.
I don’t have an ETA on when a fix will be applied but wanted to let know we have eyes on this. I’ll try to update this thread if I find out anything else.
Thanks for everyone’s patience and understanding while this is sorted out.