STS fails to start after installing extensions on OSX

[Martin Lippert]

Hey nomad!

Thanks for the additional details. I usually install and run STS on my OSX machine with the admin rights user, so it is easily possible that I never came across those permission problems you are seeing. I will go ahead and try that as well. In the meantime, whenever you find some more details, let us know.

Thanks,
Martin

[mcarrier]

Using: STS-2.9.2.RELEASE on Lion

Installed STS to ~/springsource as a user with admin rights (and I only use the tool suite as the same user) with some success for a while. I needed to install the XCode command line tools for mac ports and after the next restart "boom", STS cannot be started because it is damaged or incomplete.

Permissioning looked aright @ 755 throughout. I also have not tried the .ini suggestion because I am unsure of where I can find a valid copy to replace it with. Here is the current content of the sts.ini file:

-startup
../../../plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
--launcher.library
../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx_1.1.101. v20120109-1504
-product
com.springsource.sts.ide
--launcher.defaultAction
openFile
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Xmn128m
-Xms256m
-Xmx768m
-Xss1m
-XX:PermSize=128m
-XX:MaxPermSize=384m
-XstartOnFirstThread
-Dorg.eclipse.swt.internal.carbon.smallFonts

Another interesting fact: if I run the STS symlink directly it runs fine, but clicking on the application pops up the message above.

Hope this helps!

[Martin Lippert]

Hey!

It is strange that the installation of the Xcode tools from Apple causes this kind of problem. The content of the sts.ini file looks ok. What happens if you rename sts.ini to STS.ini? And what happens with a fresh installation of STS? Does that work? (just trying to find out where the problem might be)

-Martin

[mdorey]

I noticed this problem on a clean install of STS (springsource-tool-suite-2.9.2.RELEASE-e3.7.2-macosx-cocoa-x86_64-installer.dmg) on OSX Lion 10.7.4.

I installed into /Users/<username>/springsource/

I'm unable to launch STS using the app icon but using the STS symlink directly in the terminal works fine.

Edit: I fixed the issue by running chmod on STS.ini in /Users/<username>/springsource/sts-2.9.2.RELEASE/STS.app/Contents/MacOS

chmod 664 STS.ini (by default STS.ini has 644).

[SnarfMax]

Maybe I don't know what I'm doing from the command line but, I just went into the .../STS.app/Contents/MacOS dir and typed "chmod 664 STS.ini" - is that right?

If so, it didn't work.

Anyone have any other suggestions?

[SnarfMax]

Update: I just installed the 64 bit version and it worked!

[Martin Lippert]

Hey!

Glad to hear you got it working. But why didn't the 32bit version work for you? Do you have a 32bit JVM installed and active or just a 64bit one?

Cheers,
-Martin

[isharamet]

Hi, everyone!

I have the same problem with 2.9.2 (64bit) on Mountain Lion. I mean the 'You can’t open the application “STS” because it may be damaged or incomplete.' problem. But STS starts normall using symlink or running executable directly from .app package.

[Martin Lippert]

Hey!

The message "You can’t open the application “STS” because it may be damaged or incomplete." when running Mountain Lion is caused by the new Mountain Lion feature "Gatekeeper" and because the latest STS releases are not yet signed in a way that Mountain Lion recognizes this app as ok. But I think if you ignore the message, you should be able to run STS using the default "click on the app icon" way.

We will try to get this fixed for STS 3.1.0, scheduled for October. See also:
https://issuetracker.springsource.com/browse/STS-2801

Cheers,
-Martin

[Stone]

I've had the problem with both 2.9.2 and now 3.0.0 running on Lion. A co-worker said the same thing occurred to him, but only after selecting the Launch checkbox after installing. Sure enough, I left that checkbox unchecked and it all worked fine. Not sure what that automatic launch does, but there's something in there that messes things up.