System
-
Mac: MacBook Pro, Apple M2 Pro
-
macOS: 26.6.2 (25G83)
-
Battle.net App: 2.52.11.17778 (current)
-
The shipped Mac client binary is x86_64-only (verified with
lipo -infoon the app binary andbattle.net-core.framework), so it runs under Rosetta 2 translation on Apple Silicon.
Primary symptom — deterministic crash on login
100% reproducible. Confirmed across three client versions (2.52.8.17651, 2.52.10.17731, 2.52.11.17778) and across a macOS update (26.5.2 → 26.6.2). 9 crash reports generated, all with identical signatures.
Sequence from the app’s own log:
-
Credentials submitted → token received (
UAuth: status changed: ReceivedToken) -
Connecting to server. address=us.actual.battle.net port=1119 -
Immediately after, the client redirects back and re-renders a login credential screen a second time — sometimes the password screen, sometimes the email-OTP screen (varies per attempt; crashes either way)
-
The moment that second screen renders, the app dies and the “Blizzard Error” dialog appears — a small window titled Blizzard Error reading “The application encountered an unexpected error,” with a description box, a “Send to Blizzard” checkbox (left enabled), and a Report ID. One such submitted report: 70AFC01C-5D71-4A20-91EA-9EFD1B09C9DA
The crash itself:
EXC_BAD_ACCESS: KERN_INVALID_ADDRESS at 0x0000000000000000
Thread "CrBrowserMain"
0 net.battle.app.framework Run + 31664202
1 net.battle.app.framework Run + 32264314
...
14 QtCore QMetaObject::activate(QObject*, QMetaObject const*, int, void**)
15 QtCore QTimer::timerEvent(QTimerEvent*)
16 QtCore QObject::event(QEvent*)
17 QtWidgets QApplicationPrivate::notify_helper(QObject*, QEvent*)
A null-pointer dereference inside the app’s own Qt/CEF UI code, in a timer callback — not a driver, GPU, or OS-level fault.
One attempt captured an explicit race condition in the log:
Connecting to server. address=us.actual.battle.net port=1119
Attempted connection when already connected: disconnecting
error=ERROR_INVALID_ARGS (7)
error=ERROR_TOKEN_NOT_FOUND (49)
suggesting the client opens an overlapping/duplicate connection to the login service, which appears to trigger the redirect-and-crash.
I’m able to share full crash reports if you would allow me to leave pastebin links:
-
Current build 2.52.11.17778
-
Earlier build 2.52.10.17731
Secondary symptom — Error BLZBNTBGS80000011 (3018)
Happens only sometimes; the crash above occurs on the other attempts. Login hangs ~60 seconds, then a dialog appears reading: “We couldn’t log you in to Battle.net. While you are offline, friends & chat will be unavailable, and you will have to log in when playing games or accessing account management.” — followed by “You may try again in 33 seconds.” and Error Code: BLZBNTBGS80000011 (3018).
The log maps this to ERROR_RPC_DISCONNECT, occurring after the client loaded an email-OTP page (.../login/en/email-otp?suppress-auto-email-otp=true) that received no response before the RPC session timed out.
Key behavioral clue
Launching Battle.net while offline works perfectly — the UI loads fully with no issue. The failure only occurs once the app attempts a live login/connect cycle. This isolates the problem to post-authentication connection handling, not app startup or rendering generally.
Troubleshooting completed — no effect
-
Clean reinstall multiple times, including full wipe of /Users/Shared/Battle.net,
~/Library/Application Support/Battle.net, and~/Library/Application Support/Blizzard -
Tried logging in against both US and EU regions — both fail identically
-
Created a brand new Battle.net account — same failure
-
No parental controls on the account
-
Logged in successfully via browser at account . battle . net — no change to app behavior
-
macOS Application Firewall confirmed disabled
-
No VPN; no proxy configured (verified via
scutil --proxy/networksetup) -
No third-party security software installed
-
Reset network devices, flushed DNS, released/renewed IP
-
All software, drivers, and firmware current
-
Multiple crash reports already submitted through the in-app “Send to Blizzard” reporter