Codekit Crashed on Startup (Every Time) Won't Open #520
Comments
|
Something has modified codekit’s App bundle so that the code signature is now invalid. Delete the app and download a fresh copy from codekitapp.com Make sure you’re not running any antivirus garbage, and that you do not use a third-party app to unzip the download. |
|
I have deleted and re-downloaded the app and I'm still getting the same issues. I am running SentinelOne, but I can't turn it on or off since it is controlled by my IT department. It is not flagging it or giving any messages when I download or unzip it, so I don't think it is doing anything to it. I'm at a loss here. |
|
It’s the anti-virus app. It’s modifying the bits of the app bundle while it’s scanning, which invalidates the signature. To verify, install the app on a machine without that security nonsense running and it’ll work just fine. You’ll likely need to get your IT department involved. After you spend 20 minutes berating them for installing antivirus on macOS, get them to exempt CodeKit from the scan.
…Sent from my iPhone
On Dec 17, 2018, at 11:20, Jason ***@***.***> wrote:
I have deleted and re-downloaded the app and I'm still getting the same issues. I am running SentinelOne, but I can't turn it on or off since it is controlled by my IT department. It is not flagging it or giving any messages when I download or unzip it, so I don't think it is doing anything to it. I'm at a loss here.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Trust me, I have already berated them. Many times. I'll see what I can do from this end. Thanks. |
|
Earth hath no incompetence like corporate IT departments.
…Sent from my iPhone
On Dec 17, 2018, at 11:24, Jason ***@***.***> wrote:
Trust me, I have already berated them. Many times.
I'll see what I can do from this end. Thanks.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Hey, @bdkjones, so I have been working with my IT department on this. We have verified that our AV software (SentinelOne (S1)) is blocking it. After some trial and error, we both agree this is the cause. But we still have a problem. They have tried excluding CodeKit in S1, but it still keeps blocking it. After disabling S1 and confirming that CodeKit runs, they have excluded the path: Macintosh HD > Applications > CodeKit.app -- but it still won't launch again after S1 has been reactivated. So, they are asking, what else needs to be excluded? Is there another path? What is CodeKit trying to do that S1 is preventing even after that path exclusion? Thanks for your time and help with this. |
|
Based on the crash report, macOS is complaining that the code signature is invalid. This means that something is modifying the actual bytes of the executable when it’s launched. I don’t know how your AV works, but the /Applications/CodeKit.app path is really just a folder that the Finder presents to you as a single file. You may need to add the subpaths to the actual executable if you can’t tell the AV to ignore absolutely everything under that “folder”.
…Sent from my iPhone
On Dec 20, 2018, at 06:58, Jason ***@***.***> wrote:
Hey, @bdkjones, so I have been working with my IT department on this. We have verified that our AV software (SentinelOne (S1)) is blocking it. After some trial and error, we both agree this is the cause. But we still have a problem. They have tried excluding CodeKit in S1, but it still keeps blocking it.
After disabling S1 and confirming that CodeKit runs, they have excluded the path: Macintosh HD > Applications > CodeKit.app -- but it still won't launch again after S1 has been reactivated. So, they are asking, what else needs to be excluded? Is there another path? What is CodeKit trying to do that S1 is preventing even after that path exclusion?
Thanks for your time and help with this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
@bdkjones thanks for the help. I was finally able to get my IT department what they needed to allow CodeKit to work again for me. Much appreciated! |
|
Just so I know for future people plagued by an IT department, what was the fix? |
|
The only thing I saw that they added was exceptions for the paths:
The latter appears to be one the one that finally allowed it access. SentinelOne is VERY aggressive in it's monitoring. I have had my Adobe Creative Cloud app, Fiery printing software, and Splashtop, the remote access software IT uses to access our Macs, all flagged as well. It's ridiculous software. |
|
I had the exact same problem with SentinelOne. FWIW my IT department had to add both of those paths to the exceptions list before it worked. Thanks for sharing @jdkrause — it made my troubleshooting a little easier. |
Codekit will not open anymore. It just crashes upon startup. Actually it never even gets past a click of the icon and a second later it crashes. I have the latest version too.
Here is my crash report:
The text was updated successfully, but these errors were encountered: