WinAuth can no longer be used as an option to import the Blizzard Authenticator

[Thunderschnozzle]

Describe the bug
See title

To Reproduce
The provided steps to import the Blizzard Authenticator, as described under the "Option 2 (Windows only)" section, which I have submitted originally myself, no longer work. Blizzard changed their authenticator so that now it is part of their "Battle.net" mobile app. Apparently this messes up WinAuth's ability to import the necessary data.

I've written a new set of steps in an attempt to adjust to these new changes, but was hit with an error message. Here are the steps to recreate the error message:

1. Install the "Battle.net" mobile app from the "iOS" or "Google Play Store" and launch it.
2. Log in the "Battle.net" mobile app to your "Battle.net" account and follow any other on-screen instructions to finish setting up the app.
3. Tap on your Username at the top-left corner of the screen to bring up the app's menu and then tap on "Authenticator."
4. Tap on the "Enable" button and follow the on-screen instructions to enable (a.k.a. "attach") the "Battle.net" Authenticator to your "Battle.net" account.
   Note: This will log out all devices that are currently logged-in to your "Battle.net" account.
5. Repeat steps F-Droid Inclusion #2 + Option to use "insecure" storage #3.
6. Tap on the cogwheel button ---> "Serial & Restore Codes."
7. Write down these codes and store them in a safe place for future reference. They are required to identify your "Battle.net" authenticator for support/debugging purposes.
8. Download the "Latest" version of "WinAuth" ("WinAuth-X.X.X.zip") to your PC from https://github.com/winauth/winauth/releases and extract its contents.
9. Double-click on the "WinAuth.exe" file to run it.
10. Click on "Add" ---> "Battle.Net" ---> "Restore Authenticator."
11. Fill the "Serial" and "Restore Code" codes you wrote down in step Added Pluralsight icon #7 into the "Serial Number" and Restore Code" fields respectively, and then click on "OK"

Expected behavior
I expect not to get an error message.

App Version
1.22.0

Additional context
I know that the problem is with the WinAuth app. I just wanted to inform you about it, since, for many user who are not comfortable with python (including myself) this was the only viable option to import the Blizzard authenticator.

[jedis00]

This is still an issue. Blizzard Authenticator is going away soon and all 2FA is being disabled. The Battle.net app must be used.

[Thunderschnozzle]

I see. Good to know, since I'm using SMS 2FA right now. Thanks for the heads up 👍

[jamie-mh]

I'm not too familiar with the Battle.net system. With the discontinuation of the Battle.net Authenticator, does this mean that the 8-digit codes are going away, or is that still an option?

[Thunderschnozzle]

AFAIK (and don't quote me on this), no, it's not going away. The 8-digit code is still a thing, it's just that you have to use the "Battle.net" mobile app. It seems that they're simply consolidating the two apps, that's all. Hopefully the SMS 2FA will continue to work, because I don't plan on using their stupid app.