If you've been keeping track of various known issues for the newest Hearthstone Patch 23.2, or even had the misfortune of being personally affected by account login problems and faulty Mercenaries bounties, then you might be glad to know another one of these obstacles should be getting fully resolved.
But not via a server-side hotfix as usual, apparently this has been serious enough to require rolling out a small client patch:
Quote From DeckTech Update patch just went out on desktop, to fix the bug blocking some people from being able to login on their accounts. Going out on mobile as soon as approved by the various storefronts. Will be a download from your mobile storefront.
As is often the case with mobile updates, this could mean waiting a few hours. If you pay attention to such technical aspects: this changes the current patch build from 23.2.0.137922 to 23.2.0.138759.
The relevant passage from the official forum thread also mentions a fix for privacy settings:
Quote From Blizzard 5/11 Update:
The team has just released an update patch for desktop. The patch fixes the bog blocking some players from logging in because of an “account update.” The patch also fixes a bug that prevented privacy settings from saving across devices.The update patch will be made available to mobile devices as it is approved on those mobile storefronts.
While it was possible to deal with this problem by reinstalling the game (or apparently even by repeatedly trying to get in) - as we noted in the Launch Known Issues post - there was probably no shortage of confused players who don't keep up to date with such breaking news.
In case you experienced any brief difficulties getting into the game earlier today (at least on Americas server) and they weren't related to anything seen above, that might not've been Hearthstone's fault - apparently Blizzard's servers were also experiencing a DDoS attack, which could've resulted in high latency and disconnects for some players.
Other Recent Hotfixes
While we've been keeping our recent posts on ongoing known issues up to date, perhaps you haven't had a chance to catch the info on the latest batch of hotfixes. We'll list them below for your convenience.
Anything else can be found in the previous articles on the topic:
- [Updated] Hearthstone’s 23.2 Patch Arrives With Known Issues
- Emergency Hotfix for Mercenaries Crashes & Card Effects
Quote From Blizzard
- [Updated 5/11]: The team is investigating reports of players unable to enter certain Bounties (such as the Mi’da Bounty as part of the N’Zoth event). It appears that this error happens when the Bounty was unlocked by defeating on the previous Bounty (or Bounties) only on Heroic. While the team works on a permanent solution, a workaround to this issue is to go back and defeat the preceding Bounty (or Bounties) on Normal and then return to the one you are unable to access.
- [Added 5/11]: The team is aware that the frame rate dropdown can’t be fully utilized on some mobile devices.
- [Added 5/11]: The team is aware that some Rexxar Mercenaries Portraits appear to have feigned death. The team is working on a fix for players who lost access to those Portraits to get them back. Any players who lost Rexxar Portraits from this bug and then received those same Portraits again before the bug is fixed will get awarded a different Rexxar Portrait with the bug fix (or, if all Rexxar Portraits are owned, Rexxar Coins).
Not mentioned in that official forum thread but known to Blizzard, Nellie, the Great Thresher is also still misbehaving, just like before the patch. You might've even caught a mention of this in one of our recent forum threads.
Team's looking into this. Does the same workaround of just restarting when they play it work like before? Yes sir, quitting the game right away and launching still gets you into the game.
Man, the game just cannot take all these cheap Pirates. Everyone knows it's always Mr. Smite anyway, our own modern version of Huffer.
Good luck getting in and actually being able to play the game, if you couldn't before!
Comments
I got the account needs to be updated message once, then no issues afterwards. I thought there was some actual account update with this patch.
Thanks for the update. I was affected by the (apparent?) DDoS attack and was simply baffled as to what was going on.
Toki, Time-Tinker: Unprecedented time