Howdy howdy;
EDIT: Whoever the developer is behind this error log: spooky magic for /Applications/World of Warcraft/_retail_/World of Warcraft.app/Contents/MacOS/World of Warcraft (0xbebafeca) at text offset: 0, you’re hilarious.
EDIT: This is genuinely meant to try and help the dev team at Blizzard, not as an angry rant; sure, it’s a bummer that I can’t play, but I’d still like to try and help find a solution in whatever way I can.
I ran some diagnostics to see what errors are popping up for me when I replicate the issue.
Here are my specs:
2020 MacBook Pro, model ID 16,2
2.3 GHz Quad-Core Intel Core i7
Intel Iris Plus Graphics 1536 MB
16 GB 3733 MHz LPDDR4X
Here’s some of what I found in the diagnostics:
The WoW app is getting some tccd errors for me, which indicates that it may have some authentication problems going on.
TCCDProcess: identifier=com.blizzard.worldofwarcraft, pid=14926, auid=501, euid=501, binary_path=/Applications/World of Warcraft/retail/World of Warcraft.app/Contents/MacOS/World of Warcraft attempted to call TCCAccessRequest for kTCCServiceAccessibility without the recommended com.apple.private.tcc.manager.check-by-audit-token entitlement
Looks like that error is related to this system function call here:
FAIL: PID[14892]: SecTaskCopySigningIdentifier(): no signing identifier
Which implies that somewhere, WoW doesn’t have the right permissions to access something, or the way it is accessing it is deprecated/invalid.
I saw this warning message in the World of Warcraft process that indicates a MacOS specific error, related to security/privileges:
WARNING: Secure coding is not enabled for restorable state! Enable secure coding by implementing NSApplicationDelegate.applicationSupportsSecureRestorableState: and returning YES.
I’m not familiar with WoW’s codebase, so I don’t have much insight on that warning message.
I did notice this bit of the streaming handshake with Blizzard servers:
New flow: NEFlow type = stream, app = com.blizzard.worldofwarcraft, name = launcher.worldofwarcraft.com, xxx.xxx.xxx.xxx:x ↔ 137.221.106.103:80, filter_id = , interface = en0
It looks like it could be trying to stream data through HTTP and not HTTPS, so the data would be unencrypted. Not sure what all is being sent over that connection, or if it’s related, but it’s still something to note in case that’s a security concern.
Because this error seems to be connection-based (the app crashes for me right as the little textbox that says “Connecting” pops up), I would say - however silly it sounds - you may want to check and/or renew some signing certificates.
There’s also another error here:
AddInstanceForFactory: No factory registered for id <CFUUID 0x6000034270e0> F8BB1C28-BAE8-11D6-9C31-00039315CD46
So something on the loading screen seems to be using the CFPlugin API and is throwing an error as well, which would probably be something in the login screen that other open source developers might be allowed to play with. I don’t think that would crash the program, though.
In all, it could be an auth issue causing the crash.
Not necessarily just network authentication and SSL, either; the app could be attempting to access something hardware-related that it hasn’t received privileges for, because privileges for certain things may now be handled differently in Sonoma.
Source: This could all be wrong, because I am a moron; but as a software developer, I would still breathe my deep, jaded sigh, and check to see if I forgot to include my “license to partake in shenanigans” within my app architecture.