osx app did not open
bendyarm opened this issue · comments
I am on osx 10.8.5 Mountain Lion.
I expanded CodePulse-1.0.1-osx.zip and moved the .app/
under /Applications/
I double-clicked on the .app and nothing happened.
I did "top" in a Terminal and tried again and I did not see anything show up.
Also tried looking in Activity Monitor. Nothing there, either.
Are there some package dependencies? I didn't notice them in the doc,
but maybe I didn't look in the right place.
-Bendyarm
For OS X support we've been testing this on 10.9.2. Not sure what could be going wrong with Mountain Lion. We'll try and see if we can get our hands on a machine with an older OS X version to try it out. In the meantime do you have a more recent OS X version to try Code Pulse with?
@bendyarm I just tested Code Pulse on a vanilla Mountain Lion 10.8.5 installation and it opened up right away without issue. Have you tried it again since?
Can't reproduce, closing this issue.
It wasn't coming up but I didn't know why.
Now I thought of the idea of starting it from a command line.
It turns out there is an "open" command for an app.
When I tried that, this is what I got:
bash-3.2$ cd /Applications
bash-3.2$ open 'Code Pulse.app'
LSOpenURLsWithRole() failed with error -10810 for the file /Applications/Code Pulse.app.
bash-3.2$
-bendyarm
I tried Oracle java version "1.7.0_21";
looked through Info.plist; and checked various other things
that people found who had run into this error on other apps.
All to no avail.
But then I saw you have a new version 1.1.1 so I tried that and it worked!
One other thing: the OWASP front page has a minor typo: "donload" should be "download".
We package a private JRE within Code Pulse's resources so in theory the version of Java you have installed on your system (if at all) has no impact on how Code Pulse ends up running.
Happy to hear that 1.1.1 ended up working for you! Quite frankly we don't think we changed anything that would have impacted the problem you described, but I'm not going to argue with good news.
And thanks for the typo you pointed out. I just fixed that.