[Main Thread] Crashes on launch after maintenance Jan 24th

Any response from Blizzard???

The only to actually create urgency for this issue is to cancel

8 Likes

^ Everyone should cancel subs… Already have.

8 Likes

So frustrating. I’ll bet they don’t have any older machines much less older machines with older OSs to test on. They’re probably flying blind.

2 Likes
3 Likes

I have updated my iMac to 11.7.3, can’t go beyond that and right now I cannot afford a $1800 mac for a game. That’s the price for a 2020 iMac. A refurbished 2018 is around $350 but I know for experience that in 2 years it’ll be old and Blizzard might come with a new update that will require faster and more potent computers. What’s really frustrating is that 2 days ago I was able to play without problems.

5 Likes

basically what we know already. Yadayadayada “We are aware and looking into this, upgrade to Monterey or Ventura if possible”

But the EU-Support seems to be more active, they got a couple of blue posts, spanish speaking one as well.

1 Like

Really hoping for a fix soon! Just adding another voice to let them know there are lots of us waiting. :slight_smile:

4 Likes

really hoping to play this game i pay for soon… one more in the q

1 Like

The cause has been identified and now it’s just a matter of convincing live ops a fix that’s mac specific is important enough to do a straight to live rush. (they only put a rush on new builds for most serious of issues, otherwise they usually stage/test fix on ptr first then sync it to live after a couple days)

So basically, you’re about to see just how important mac only issue is.

12 Likes

I’m a forum noob. Do you work for blizzard? How do you know they found the cause?

3 Likes

Tell 'em if they take a few days they owe us an extra vault, free game time, etc etc. A few days could be the next reset! That’s too long.

4 Likes

Sooo this is what I got from BlizzardCS on the issue with MacOS logging issue:

Greetings,

Thank you for your patience while we looked into your issue for you during this longer than normal wait time. Due to multiple product launches in short succession, we have a higher than normal ticket queue. We’re working as hard as we can to get this under control now. In an effort to get the majority of players assistance as quickly as possible, we wanted to send you an automated message which may help with this lockup/crash issue to prevent you from waiting too long to reach an agent. This is being sent due to the category that you submitted your ticket under, but if it does not describe your issue, please reopen the ticket with new copies of the files requested in the second half of the reply.

Before talking about troubleshooting, please note that if your contact is about Call of Duty products, Blizzard customer support is unable to assist with this type of contact. We can help handle payments, Battle.net account issues, and any errors with installation and patching, but that’s the extent of the help we can provide. Once the game data is installed on your PC, anything with the game client such as crashing needs to go to Activision for support. The reason for this is that it’s their game, and they’ll be the most familiar with known bugs and what sorts of things might cause this problem for you. If you suspect the problem is due to a bad installation, you can attempt to repair or reinstall the game, but beyond that please use the link below to contact Activision for help.

For issues with the battle.net application failing to launch, locking up and becoming unresponsive, or crashing, we usually find that a few specific things cause the vast majority of problems. Usually this is going to be caused by an out of date program (drivers, an operating system, or security), a conflicting program, or an issue with the application being corrupted. Our best tips for fixing this are listed at the article below. If the first set of steps don’t fix you up, click the expandable “carrot menu” for more advanced troubleshooting.

This should help you resolve the problem, but if not, we’ll need some more information to help you identify the problem. Please create a new copy of your system files. PLEASE NOTE: our system automatically deletes files over a certain age, so including fresh files is critical to having the issue resolved as soon as possible.

If you attach these to your ticket and reply with the exact error code you currently receive (if any), we can look for more options. We appreciate you once more for bearing with us during this launch. Should you need more help with this error, please don’t hesitate to reopen this ticket and someone will assist you as soon as humanly possible.

Links would probably work…if I was on a PC. So now I guess we keep paying to wait. (sorry, no Blizzard links were allowed to make this post)

1 Like

I got this as a reply to my ticket :

I’m one of the specialist technical support Game Masters at Blizzard. Thanks for getting in touch and letting us know about the crash.

I can understand that this is frustrating. I’ve looked into this for you and the issue you encounter is a bug, that is already being looked into by our developers.

Some players say it helps updating the Mac OS to Monterey (12.0) so you may want to try this.

If you rather not update your operating system, we can only ask you to be patient.

I hope these steps resolve the issue for you and I wish you a great day.

Should you have any other questions or concerns, please do not hesitate to contact us again.

1 Like

Same Issue here. I followed ALL Trouble Shooting Steps provided by Blizzard. Nothing…
IMAC (Retina 5K, 27Inch)
Processor: 4GHz Quad-Core INTEL CORE i7
Memory: 32GB 1600MHz DD3
Graphics: AMD Radeon R9 M290x 2GB.
7398C424-C373-4C1E-A1A8-067D8059B0BD

I have direct lines of communication. I don’t work at blizzard but work directly with them to test things and give feedback. I’m also pretty good at guessing causes and in this case I was pretty much right. The cause was client accessing an api that doesn’t exist on macOS below 12.x or higher. It’s another one of those situations where a design that isn’t considering apples update policy added something to game without recognizing it’d break older OSes on macOS (cause this typically doesn’t happen on windows side).

Microsoft doesn’t cut off support for last version of OS immediately upon release of new one like apple does. Like as soon as 13.x shipped 12.x was dead in water outside of security fixes. No bug fixes, no driver updates, no back porting of api changes. Where as windows 10 gets top notch support despite fact 11 is out…

Basically, designer added something that couldn’t run on old macOS versions but could run on old windows so it was missed by QA regression testing because mac testing leaves much to be desired because again mac support is pretty skeletal.

What they’ll likely do is add a macOS specific check that says “if macOS version old, don’t try to load this missing api” which will result in no longer crashing but likely whatever visual that needs this new api to be invisible or look funny to users not on latest macOS (which in itself may not be ideal but at least it runs).

At end of day, apple does put developers in a tough spot with the way they rapidly deprecate old OS versions AND hardwares access to new versions. “oh so you haven’t bought a new mac in 5 years? no more OS updates for you, but also we’re not gonna update the old OSes either to ensure you can still run latest software, so you better just buy a new mac”. that’s apples bottom line and I don’t fault blizzard or any other dev for issues this causes.

Of course that said, I still prefer macOS because it’s where my productive environment is. The software I like (such as BBEdit) is at.

I will say this, people who are holding out on updating macOS, who CAN update macOS, should probably do so sooner or later, at least up to 12.x. I can understand avoiding ventura a little longer while it irons out some issues, but being on 10.14, 10.15, 11.x, will be a significant hold back as wow and other applications move away from these OS versions.

18 Likes

Well, it’s hard to see if it’s “important enough” from a company’s perspective…but I imagine a lot of people here have been working hard during Dragonflight to get ahead in PVP and PVE…and vaults are really important for that…I would hope that the importance to the players is taken into account, especially some of us that have been playing well over a decade and a half as loyal customers and fans…

5 Likes

Understand your point, but wouldn’t it be nice if a “Blue” would provide a response on the issue. Right now frustration is building with clients, due to a lack of response is equating to a lack of concern. I miss the days of Ghostcrawler and the other blue posts that kept the players in the loop. The “it’s not our problem, but somebody else’s” is a horrible way to work the issue. This is a global multi-billion dollar company not the start-up from the 90’s. Even back then Blizzard’s customer service was more engaging with the client. Ahhh, the good ole’ days. Just making a point in the discussion.

5 Likes

They’ve given 3 responses, with latest being this morning. The thread just moves so fast they get buried. See that blizz button on right? you can click it and move between blizzard replies to find them easier. Is it as verbose as mine? no, but that’s cause CS is usually not as well informed as the tech mvps or actual developers because they’re spread thin too, between MANY issues. Gotta remember ABK downsized them too not long back and they’re also often spread thin. :\

11 Likes

so when are we going to stop hearing excuses and get the result? there’s a saying… excuses are just like a***holes everyones got one.

3 Likes