After updating to 2.8.0 today, the game will not launch. I am playing on older hardware, and if the minimum system requirements have changed, they need to be updated in the forthcoming patch notes, and on the shop page.
Scan and Repair, uninstall and reinstall does not resolve issue.
If Blizzard has moved to a newer version of XCode to keep up with Apple’s newer hardware, then the game is no longer going to be playable on anything below Big Sur (macOS 11). That would be the “life support” OS version which means the next major shift in XCode will likely make Monterey the lowest targetable OS.
Bottom line, Big Sur is probably the new “unsupported/life support” minimum and Monterey is the new official minimum on macOS.
While this is a likely explanation, and also the first thing that occurred to me, it’s also factually incorrect. I have a bit more skills than the average user so I ran it from the CLI to see what the actual error was:
/Applications/Diablo III/Diablo III.app/Contents$ MacOS/Diablo\ III
2025-02-05 03:12:57.836 Diablo III[28542:13810095] No Info.plist file in application bundle or no NSPrincipalClass in the Info.plist file, exiting
The Info.plist file exists and is indeed lacking this key. It also contains this:
DTPlatformVersion
13.1
DTSDKName
macosx13.1
LSMinimumSystemVersion
10.13
OK, that’s at least more reassuring for those on older systems still. That means they forgot to set the key in the XCode project. Anyone with XCode with the command line tools and optional packages downloaded could just load up that file, create the NSPrincipleClass key and set the data value to String with the string being NSApplication (this sets the bundle to launch as macOS - in iOS it’d be UIApplication).
Since you are likely to have XCode installed, you might want to try adding that key to the info.plist file. It’s easier to do so via the plist editor there than via manual text entry into the file.
I just tried this, and I was able to launch D3 after some dabbling, although I edited it with a text editor (which is a better solution in this case anyway).
It IS quite the mess though, and Battle.net will be fighting you all the way. Once you edit the plist file Battle.net will offer an update (which is to revert the plist file to the broken version again).
What you need to do is this:
Open /Applications/Diablo III/Diablo III.app/Contents/Info.plist with a text editor
Add the following lines at the bottom, right before the </dict> tag:
<key>NSPrincipalClass</key>
<string>NSApplication</string>
DO NOT CLOSE THE FILE OR YOUR EDITOR, KEEP THEM OPEN.
Save the file. Again, do NOT close your editor.
Battle.net will offer an update. Let it update, and save the file in your editor again.
Rinse and repeat the last step until you get a Play button in Battle.net and the file is saved.
Didn’t work. Used text edit in macOS Catalina. How does “rinse and repeat” work? Battle net rewrites the file every time. Also, I have a “Play” button enabled as usual but it won’t launch the game. Also the file Info.plist was not where you indicated. What OS are you using?
It’s the “next day” and even though the key/string data is in the Info.plist file, the game will not launch. Getting the same Play > Launching > Playing Now > Play cycle. Before I opened the Info.plist to check that it was the same, I was simply getting the application had crashed dialog.
However, I’m getting a “Downloading Additional Content” message on the game startup screen… and it’s taking a long time. What’s that about?
“Rinse and repeat” means that after you save the file, Battle.net will pick up it has been changed and change the Play button to Update. You need to click this in order to be able to launch the game, and after it has restored the file back to the broken version you save again. You “Rinse and Repeat” these steps until Battle.net doesn’t pick up your change and you can hit Play before it changes to Update again.