Mine is saying a fatal error has occurred. The Battlenet app lets me complete the scan and says there is nothing to repair. It says there are no updates too.
4 Likes
704985B3-A967-4C4D-82FF-5D60465D8CB4
Crashes at the same place each time - the authentication screen. When working, the indicator spins, but today the Authentication Screen has no spinning and crashes almost immediately
3 Likes
238DB090-7E2A-4646-9FCB-8A2CC0C979F1
Crashes at the same time as everyone else. Same thing played this morning came back could not. I am a Mac User as well. I notice one thing different though when its says connecting the symbol next to connect doesn’t move, it usually does for me.
2 Likes
Any updates on the fix for this?
6 Likes
Same issue as this thread
3 Likes
I too have the same issue. A9C169AD-6B0D-4455-9A5D-8C51956BD9C6
Something related to the BlizzardBrowser.app:
/Applications/Heroes of the Storm/*/BlizzardBrowser.app/Contents/Frameworks/BlizzardBrowser Helper.app/Contents/MacOS/BlizzardBrowser Helper
Crashed Thread: 0 CrGpuMain Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000058
Exception Codes: 0x0000000000000001, 0x0000000000000058
Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [1473]
VM Region Info: 0x58 is not in any region. Bytes before following region: 140723034816424
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
mapped file 7ffca2808000-7ffcb193c000 [241.2M] r-x/r-x SM=COW ...t_id=6be86993
Thread 0 Crashed:: CrGpuMain Dispatch queue: com.apple.main-thread
0 <translation info unavailable> 0x102944620 ???
1 Metal 0x7ff81ee5dcb4 MTLResourceListAddResource + 131
2 libsystem_platform.dylib 0x7ff815308603 _sigtramp + 51
3 AppleMetalOpenGLRenderer 0x10e65a7fc GLDPixelConverter::readPixels(id<MTLDevice>, id<MTLComputeCommandEncoder>, GLGOperationRec const&, id<MTLBuffer>, unsigned long, id<MTLTexture>, MTLRegion) + 806
4 AppleMetalOpenGLRenderer 0x10e66b6ce GLDTextureRec::readTextureDataCore(unsigned int, unsigned int, unsigned int, unsigned int, unsigned int, unsigned long, unsigned long, unsigned long, unsigned long, unsigned long, unsigned long, bool, int, int, GLDPixelModeRec const*, void const*, GLDBufferRec*, bool) + 3382
5 AppleMetalOpenGLRenderer 0x10e686a53 gldReadFramebufferData + 553
6 GLEngine 0x7ffa2d294c8e glReadPixels_Exec + 1114
7 libGL.dylib 0x7ffa2d24d9d4 glReadPixels + 42
Tested on another Mac with an older version of the Battle.net launcher and it also did not work. So its broken in:
Battle.net version 2.21.1.14206
and
Battle.net version 2.22.0.14235
Tested on M1 Ultra and x86 Macs, broken in both.
Diablo 3 also freezes and I’m unable to exit.
Hearthstone works.
5 Likes
Same issue here, played two days ago with no issues running Catalina 10.15.7 iOS.
Scanned files, reinstalled game, restarted computer/battlenet and no luck.
Responds when downloaded on Mac
error code 43F1E193-0388-480D-B7CC-1BD27DF5D17E
Same problem here.
MacBook Air 2020 M1. Ventura 13.4.1
CB770E89-308A-4DCB-A079-004240AD91F3
Hello again everyone,
Thank you all for the reports and error codes that have been shared. We have passed along the info to our engineers and they are investigating the source of these crashes affecting all MacOS versions.
At the moment we do not have a work around to prevent the crash, but once we have have more info to share we will provide an update in this thread.
5 Likes
Must be really difficult to reverse whatever you did to the login servers.
2 Likes
In such complicated software as Blizzard has you should consider all services, apps and dependencies between them before doing a rollback.
Sometimes it’s not easy to just rollback a deployment that caused a bug without rolling back other recently released features and/or potentially affecting other services that might depend on these features.
So usually it comes down to evaluating pros and cons of a rollback.
In this case it seems like a feature that they introduced yesterday has more value than users affected by the bug. So perhaps rollback is not possible (or not preferable) and they have to properly fix the bug, which takes some time.
1 Like
What’s fascinating is that they appear to have made a server-side change that completely broke HOTS, Diablo III, and maybe other games for all Mac users. The fact that this easily detected outcome was not caught in testing says a lot about their QA and release cycle.
5 Likes
Error code: 0B02B4FB-93DB-435B-BCBB-65520084EFCC
I was able to log in…yay
Are you guys able to play Hots yet?
1 Like
it’s not looking good brev
1 Like
No luck yet.
Battle.net 2.2.0.14235
Agent 2.31.0.8320
same here,
Macbook M1 Pro 14’’ 2021
error code : F3088EC8-DB39-4386-BB45-C780CA721FD0
Hey all,
As some of you have discovered already, some changes were made on the back-end to alleviate the crashes when logging in with the Mac client. You should all be able to launch the game and resume playing.
Apologies for the interruption! Thank you all for hanging in there and do let us know if any new issues arise.
11 Likes