Open clun opened 3 years ago
This is not a known issue here, so we might need to try a few things. One idea would be to re-install a fresh copy of the Spring Tools 4 for Eclipse 4.11.1. If that doesn't help, you could try to remove the quarantine flag from the app via a terminal, then:
sudo xattr -r -d com.apple.quarantine SpringToolSuite4.app
(or the full path to the SpringToolSuite4.app
)
Does that help?
I have the same situation. Removing the quarantine flag didn't resolve it, still the same CODESIGNING error. Here are the Mac error details with the quarantine flag removed. Any assistance is greatly appreciated.
Process: SpringToolSuite4 [57796]
Path: /Applications/SpringToolSuite4.app/Contents/MacOS/SpringToolSuite4
Identifier: org.springframework.boot.ide.branding.sts4
Version: ???
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: SpringToolSuite4 [57796]
User ID: 502
Date/Time: 2021-10-14 08:22:09.494 -0400
OS Version: Mac OS X 10.15.7 (19H1419)
Report Version: 12
Anonymous UUID: 0C4520C7-A948-B47D-B1A9-D0C4D707F241
Sleep/Wake UUID: 2C5116B6-0683-462C-8FF9-DE540C97E68C
Time Awake Since Boot: 26000 seconds
Time Since Wake: 5500 seconds
System Integrity Protection: enabled
Crashed Thread: 0
Exception Type: EXC_CRASH (Code Signature Invalid)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: Namespace CODESIGNING, Code 0x1
kernel messages:
VM Regions Near 0 (cr2):
-->
__TEXT 0000000007dc1000-0000000007dc5000 [ 16K] r-x/r-x SM=COW
Thread 0 Crashed:
0 ??? 0x00000000114f0000 _dyld_start + 0
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x0000000000000000 rcx: 0x0000000000000000 rdx: 0x0000000000000000
rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x0000000000000000 rsp: 0x00007ffee7e42c20
r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000000000000 r11: 0x0000000000000000
r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000
rip: 0x00000000114f0000 rfl: 0x0000000000000200 cr2: 0x0000000000000000
Logical CPU: 0
Error Code: 0x00000000
Trap Number: 0
Binary Images:
0x7dc1000 - 0x7dc4ff7 +??? (0) <BF0BAA93-FE7A-3039-AC22-E0007DC821F4> (null)
0x114ef000 - 0x11581267 +??? (750.7) <0191F040-B591-3082-B8D9-498DC11D3BB5> (null)
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 18893
thread_create: 0
thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=856K resident=0K(0%) swapped_out_or_unallocated=856K(100%)
Writable regions: Total=8404K written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=8404K(100%)
VIRTUAL REGION
REGION TYPE SIZE COUNT (non-coalesced)
=========== ======= =======
STACK GUARD 56.0M 1
Stack 8192K 1
__DATA 232K 3
__DATA_CONST 20K 1
__LINKEDIT 252K 2
__TEXT 604K 2
shared memory 8K 2
=========== ======= =======
TOTAL 65.1M 12
Model: iMac18,3, BootROM 429.140.8.0.0, 4 processors, Quad-Core Intel Core i5, 3.5 GHz, 16 GB, SMC 2.41f2
Personally a fresh install of STS + dropping the .metadata
of the workspaces was the solution.
Thanks for the suggestion. I re-installed the latest STS 4 but didn't remove the .metadata directory. Now, STS starts without the error.
I have the same issue. The reinstall work a couple of day and failed again. My mac is on Big Sur (11.6)
It try to resign (cf stackoverflow link STS because, it's the root cause, but it's failed too with package
`$ codesign --force --deep --sign - /Applications/SpringToolSuite4.app
/Applications/SpringToolSuite4.app: replacing existing signature /Applications/SpringToolSuite4.app: bundle format unrecognized, invalid, or unsuitable In subcomponent: /Applications/SpringToolSuite4.app/Contents/MacOS/net/bytebuddy/byte-buddy/1.10.22 `
For test, I have reinstall a version already downloaded in my folder ~/Downloads, and the codesign command failed that I have explained before.
This time, I downloaded the last version of STS (spring-tool-suite-4-4.12.0.RELEASE-e4.21.0-macosx.cocoa.x86_64.dmg), and for testing, I will retry codesign command, and it works ...
` codesign --force --deep --sign - /Applications/SpringToolSuite4.app
/Applications/SpringToolSuite4.app: replacing existing signature `
It's strange because dmg package are same. I have checked with md5 ...
`
$ find . -name 'spr*.dmg' -exec md5 {} \; MD5 (./spring-tool-suite-4-4.12.0.RELEASE-e4.21.0-macosx.cocoa.x86_64 (2).dmg) = 6c610f658d94c17f870565c10e91f52d MD5 (./spring-tool-suite-4-4.12.0.RELEASE-e4.21.0-macosx.cocoa.x86_64.dmg) = 6c610f658d94c17f870565c10e91f52d MD5 (./spring-tool-suite-4-4.12.0.RELEASE-e4.21.0-macosx.cocoa.x86_64 (1).dmg) = 6c610f658d94c17f870565c10e91f52d
`
It seems package will change in time ... that why I need to reinstall STS every 3-4 days (or peraph after MAC restart)
I hope it's help
If you install additional plugins into the IDE, the content of the package will change, since the additional plugins will be placed into the features and plugins directory, for example.
In your comment, you mentioned that codesign failed with this message:
In subcomponent: /Applications/SpringToolSuite4.app/Contents/MacOS/net/bytebuddy/byte-buddy/1.10.22
I am surprised to see that, since the default Spring Tools 4 for Eclipse distribution doesn't come with byte-buddy stuff in that directory. The MacOS
directory should contain the launcher executable only, so it looks like some third-party plugin that you installed changed that directory and added additional stuff to it. Not sure if that helps, but since I stumbled upon it, I wanted to mention that here.
Did someone also try to disable the security checks for their developers tools via the Preferences -> Security & Privacy -> Privacy
, then select the entry for Developer Tools
. Maybe that helps?
macOS Monterey 12.x
STS 4.13.1
Finally, I want to do some search and come here. This CRASH thing happens to me for recent months, I have to reinstall STS at least once a week.
My current solution is never quit Eclipse. 😄 I will try the above methods.
I have the same issue. The reinstall work a couple of day and failed again. My mac is on Big Sur (11.6)
It try to resign (cf stackoverflow link STS because, it's the root cause, but it's failed too with package
`$ codesign --force --deep --sign - /Applications/SpringToolSuite4.app
/Applications/SpringToolSuite4.app: replacing existing signature /Applications/SpringToolSuite4.app: bundle format unrecognized, invalid, or unsuitable In subcomponent: /Applications/SpringToolSuite4.app/Contents/MacOS/net/bytebuddy/byte-buddy/1.10.22 `
Works like charm, I am able to bring STS back to life this time without reinstalling it!
I created an alias for future use, though I hope this solution is permanent and I just need it once.
alias fixsts="codesign --force --deep --sign - /Applications/SpringToolSuite4.app"
BTW, These are the plugins I've been using.
sudo codesign --force --deep --sign - /Applications/SpringToolSuite4.app
Problem solved.
I have the same issue. The reinstall work a couple of day and failed again. My mac is on Big Sur (11.6)
It try to resign (cf stackoverflow link STS because, it's the root cause, but it's failed too with package
`$ codesign --force --deep --sign - /Applications/SpringToolSuite4.app
/Applications/SpringToolSuite4.app: replacing existing signature /Applications/SpringToolSuite4.app: bundle format unrecognized, invalid, or unsuitable In subcomponent: /Applications/SpringToolSuite4.app/Contents/MacOS/net/bytebuddy/byte-buddy/1.10.22 `
my macos is ARM-64, and my problem solved. thanks!
Could you help me with this.
The first run it starts but then it keeps doing this, not asking me for any workspace locations.
Any idea, is this a known issue ? Keep investigating. T (