Due to changes in the way OS X validates code signatures, newly installed Mathematica 10.0.0 and 10.0.1 bundles do not launch on MacOS 10.9.5. This affects only users who install Mathematica after upgrading to OS 10.9.5.
Following are two different methods of resolving the problem:
Bypass the Gatekeeper system in Finder. a) Control-Click/Right-Click on the app bundle and select open. b) Wait for the verification dialog to run. c) Click OK on the next dialog to launch Mathematica.
Bypass the Gatekeeper system in Terminal. a) Launch Terminal.app. b) Set directory to the location of the DMG (i.e., cd ~/Downloads) c) Delete the quarantine attribute by evaluating the following:
xattr -d com.apple.quarantine Mathematica_10.0.1_OSX.dmg
d) Double click on the DMG and install as one normally would.
People who are comfortable with the Terminal (command-line) interface may find that method faster.
Either should be needed just once for that Mathematica.
We will be prioritizing the issue for an upcoming minor release.
I can confirm that the "xattr" command did solve my problem with Apple's quarantine process. This condition, at least in my case, stems from my preference to use all of my applications, including Mathematica, as a restricted user.
Note that these issues also apply to the 10.01 version of Wolfram Desktop on OSX 10.9.5.
A 10.9.5-compatible installer is available. See http://community.wolfram.com/groups/-/m/t/362701 .
Another workaround suggestion.
After trying to open Mathematica.app and getting the error message, go to the Security & Privacy preferences in System Preferences and click the "Open Anyway" button:
How about in 10.10?
Dangerous to predict future software compatibility.
I (me, not WRI) expect the new installer and workarounds will work under 10.10.
The Terminal solution was very simple and worked for me. Gatekeeper methods using right button or the Control key didn't work at all. Now, I'm having the usual issue with activating.
I upgraded to 10.9.5 after installing Mathematica 10. However, it is still running on the beta test license. Will this problem show up when that license expires?
From what I know of the problem, it happens when installing Mathematica 10 after upgrading to 10.9.5.
For the customer I spoke with yesterday, the first method worked (took two tries).
A re-signed 10.0.1++ is in the works, but it has to go through testing before it will be available for downloading.