Ever since the 10.1.7 updates the battle net launcher will not remember my log in info and I will have to type in my password every time I boot it up. Prior to this update, no issues at all.
I have tried clearing the cache folder for it, and it worked one time immediately after that, then went back to the issue. I also have the issue if I open battle.net, open classic, play classic for awhile, exit game, open up battle.net again and then try to go into retail wow I will have to type in PW for the launcher on 1st and 2nd start up.
I have also tried changing battle.net launcher to close after selecting game and open up again after and it has problems either way.
Just looking for anything else I could try to fix this issue. Thank you
7 Likes
Similarly, it keeps kicking me out. I have the machine and bnet launcher running “all the time”, and I’m constantly being kicked off line. Used to not do that before either.
Yep, the only change to bnet in last like 6 months, is they managed to break it even more, without fixing a single issue.
3 Likes
I’m actually wondering how long the Windows version of the Battle.net client will remain relatively unbroken (for non-update/install scenarios). I’m seeing a “security” window with no info in it and the window succeeding it is a login window with an empty password field that used to be populated by the telltale encryption dots.
I wouldn’t be the least bit surprised if this same new “feature” in the Windows client made it into the macOS client and entirely borked an already barely working login scheme.
1 Like
Yeah mac version sees security window, which does nothing, on dots no activity it just shows up, and that’s it. You have to close it and log out and back in
Yeah, on the Windows side the security window shows up but you don’t have to do the log out and back in routine. I’m kind of wondering how broken the macOS client can get since we never seem to hit rock bottom and just keep getting worse and worse and worse. I feel for the players here that have trouble, even though I also can’t really play WoW at the moment due to the UI changes. Bleh.
As it stands, you can’t patch without manually granting permissions to agent and bnet. If you do it via full disk access it’ll patch but it’ll error on fake patches (permission repairs). if you grant it developer mode then it can repair permissions too because it gets to ignore all privilege rules.
but yes fake patching never got fixed. Patching itself been busted for months. Now signin is even half busted. About only thing left to break is it launching at all.
1 Like
I get kicked out of Battle.net every time my Mac goes to sleep…
This is annoying and as you noted, problem began with Patch 10.1.7
2 Likes
I’ve found it kicks you out on the following things.
- Reboot(s) / Power Off ↔ Power On
- Sleep (yes it forces a login after a sleep)
- Your IP changes (switching from hard wired to WiFi where my external IP doesn’t change, but internal IP does change, log back in. Same happens in reverse)
And timing wise it did change around the time 10.1.7 launched as was stated. Kind of annoying.
NOTE I think the title is a bit misleading. It does save the login info (as you can quit battle.net and restart it as long as none of the 3 items above happen without having to login).
As annoying as this may be for the uninitiated, this is how software is supposed to work from a security standpoint. The fact it took this long to implement is quite frankly bizarre given the constant phishing people seem to be inundated with.
WHAT? No, this isn’t how it’s supposed to work. After sleep my laptop is locked, and all the open apps behind it are protected by that. Once it’s unlocked, my apps are all still logged in, and until a few weeks ago, so was the battle.net launcher. So no that’s not how security is supposed to work. The whole point of that check box that says “KEEP ME LOGGED IN” is me saying “don’t do this everytime”
1 Like
It’s supposed to kick you, BUT it’s supposed to use a new security feature to log back in. but THAT is broken on macOS. but working on windows. Windows logs back in, mac just shows an empty nonworking security dialog.
1 Like
It isn’t entirely functional on Windows either. It’s coded so badly that it doesn’t work half the time. Maybe the BDA would work better if it wasn’t bloatware.
3 Likes
There are some windows users having trouble with this too, seems to have gotten worse in the last week. I have a few guild members on PCs with the recurring expired login, and some posts have cropped up in the other TS forums, both wow and desktop app.
I, on the other hand, just had that new security check work for the first time this morning after taking 14.1. (I’m a risk taker, what can I say?*)
(*with a very complete Time Machine backup, lol)
Yup, I’ve been having this problem as well with the login, saves info, but not password (using windows) and every time i turn my laptop on, I have to put my password in again. Never had this problem before.
It also doesn’t help that Blizzard on top of their incompetence, have potatoes for servers.
When I cleared data and relogged a few minutes ago, a que for the launcher showed up and took a minute before I could even get in.