There must be some metadata associated with running an unknown author program for the first time which is stashed somewhere, maybe in the executable bundle itself, I don't know.
Something that causes the computer to behave differently on running it for the first time compared to subsequent times when it already knows you accepted it.
And whatever the change in behaviour is subsequent times is b0rk3n.
It's just a guess, but the reason I at least slightly expect Apple's new app security in Mavericks is that I just ditched Mavericks and reinstalled Mountain Lion.
Now, the program launches just fine, each and every time.
I don't recommend something this heavy-handed for everybody, but I've got other applications that refuse to behave correctly in Mavericks in a similar vein. Apps wrapped up in Wineskin Winery (a nice bundler tool that builds self-contained wine environments for PC executables) fails to run subsequent times under the "test run" facility, requiring a reinstall of a tiny part of the innards, and fails to run at all simply by double-clicking the wholly wrapped executable.
Mavericks does not seem to like certain kinds of third party apps, for whatever reason. It doesn't happen on recognized author apps, nor on executables you generate yourself by way of a compiler (in my limited testing).
But in any case, I wish you all luck getting it to work in Mavericks. I had to go back to Mountain Lion for this problem affecting other necessary apps, so I'm done here, until Mavericks stabilizes its security measures, or the apps catch up to whatever Apple now requires.
Pony on, all. /)
Something that causes the computer to behave differently on running it for the first time compared to subsequent times when it already knows you accepted it.
And whatever the change in behaviour is subsequent times is b0rk3n.
It's just a guess, but the reason I at least slightly expect Apple's new app security in Mavericks is that I just ditched Mavericks and reinstalled Mountain Lion.
Now, the program launches just fine, each and every time.
I don't recommend something this heavy-handed for everybody, but I've got other applications that refuse to behave correctly in Mavericks in a similar vein. Apps wrapped up in Wineskin Winery (a nice bundler tool that builds self-contained wine environments for PC executables) fails to run subsequent times under the "test run" facility, requiring a reinstall of a tiny part of the innards, and fails to run at all simply by double-clicking the wholly wrapped executable.
Mavericks does not seem to like certain kinds of third party apps, for whatever reason. It doesn't happen on recognized author apps, nor on executables you generate yourself by way of a compiler (in my limited testing).
But in any case, I wish you all luck getting it to work in Mavericks. I had to go back to Mountain Lion for this problem affecting other necessary apps, so I'm done here, until Mavericks stabilizes its security measures, or the apps catch up to whatever Apple now requires.
Pony on, all. /)