Kit fails to start after upgrading MacOS to Sequoia #1520
Comments
|
@kyen99 I have the same issue. Updated to sequoia an hour back and came across this while digging into github issues. |
|
@kyen99 @burhanrashid52 Thanks for reporting. I have a newer build working on Sequoia, just ironing out some smaller bugs. Hope to get it out by the end of the month |
|
https://github.com/script-kit/app/releases/tag/v3.1.1 @kyen99 @burhanrashid52 That link will take you to the v3 beta releases. We've tested on a bunch of machines and everything seems good to go. Please let me know if you encounter any issues on your setups though! 🙏 |
Thanks @johnlindquist. This works, however it failed to update the existing app. I had to reinstall and also needed to force repair the SDK. |
|
@burhanrashid52 is there any chance you can look through the ~/Library/Logs/Kit/main.log for the error of when it failed to update? Try and search for "error" around the timestamp when you attempted to update. I'd love to fix whatever scenario you ran into |
|
@johnlindquist This is the log I found |
@johnlindquist I installed using the macos-arm64 dmg and it worked without a hitch. |
|
I'm still getting an error in the latest pre release version seemingly because it can't find I'm using this release: https://github.com/script-kit/app/releases/tag/v3.1.12 Here's my error log output: Let me know if you need anything else. Thanks! |
|
@bmarden oh, interesting. Try this: cd ~/.kit Then open Kit again. I'll look into what could be causing the asdf shim issue |
|
Hmm, unfortunately I still get an error. Looks like it still can't find Error log[2024-10-04 15:30:34.182] [info] state.ts: 📀 Stored KENV: /Users/bmarden/.kenv ���🟢 🟢 !!!SCRIPT KIT TIME!!! 🟢 🟢 🟢 [2024-10-04 15:30:34.205] [info] index.ts: Appending switch: ignore-certificate-errors [2024-10-04 15:30:34.238] [info] index.ts: 😎 KIT_APP_VERSION 3.1.12
[2024-10-04 15:30:34.508] [info] Loading: @jitsi/robotjs [2024-10-04 15:30:35.627] [info] install.ts: 🌊 body: Launching Script Kit 3.1.12 [2024-10-04 15:30:37.495] [info] process.ts: 🎨 Parsed theme: { [2024-10-04 15:30:37.872] [info] process.ts: 🎨 Parsed theme: { [2024-10-04 15:30:37.873] [info] process.ts: 🎨 Parsed theme: { [2024-10-04 15:30:37.883] [info] jotai.ts: 0: 👂 Force input due to keyword or mainScript [2024-10-04 15:30:37.935] [info] jotai.ts: 🎨 Parsed theme: dark [2024-10-04 15:30:38.530] [error] index.ts: Error: stderr: unknown command: pnpm. Perhaps you have to reshim? [2024-10-04 15:30:38.531] [info] index.ts: 🍂 Falling back to internal terminal... |
|
Hi, I'm having some issues as well with v3 of ScriptKit. In my case it's the by ScriptKit globally installed Is there any way ScriptKit can install and use a local version of its dependencies, like pnpm? This is the error output by esbuild after pnpm is installed. And it goes away as soon as I I'm on a Mac M1, Sequoia 15.0.1. Thank you for an amazing utility! |
|
@hansgen Oh, so:
|
I figured out that the culprit was The AWS CDK cli commands started working again after uninstalling (just) |
|
@hansgen hmm, trying to think how to handle this scenario. It uses the default pnpm install script: https://github.com/script-kit/app/blob/main/src/main/install.ts#L588 (which is the same as https://pnpm.io/installation#on-posix-systems ) Can you remove pnpm from your ~/.zshrc or ~/.bashrc instead? Script Kit should be able to access it even if it's not loaded into the PATH |
|
I've been doing some more investigation. The issue isn't Timeline: Before I did anything, I pulled the source code for Restarting with a "clean" system, i.e. removing ~/.kenv, ~/.kit, ~/Library/pnpm/ and PNPM paths in ~/.zshrc, I start Script Kit (3.1.12) anew. Script Kit does its setup (installing pnpm, node etc) I open a new terminal (formatted for clarity): ❯ printenv | grep node
PATH=/Users/hans/Library/pnpm:/Users/hans/.nvm/versions/node/v18.19.1/bin:/opt/homebrew/bin:/opt/homebrew/sbin: .....
NVM_BIN=/Users/hans/.nvm/versions/node/v18.19.1/bin
NVM_INC=/Users/hans/.nvm/versions/node/v18.19.1/include/node
❯ which node
/Users/hans/.nvm/versions/node/v18.19.1/bin/nodeI cd to my project folder, run the I do ❯ printenv | grep node
NODE_PATH=/Users/hans/Library/pnpm/nodejs/20.17.0/bin/node
PATH=/Users/hans/.nvm/versions/node/v18.19.1/bin:/opt/homebrew/bin:/usr/local/bin:/Users/hans/Library/pnpm:/Users/hans/.nvm/versions/node/v18.19.1/bin
PATH_FROM_DOTENV=/Users/hans/.kit/bin:/Users/hans/.kit/override/code:/Users/hans/.kenv/bin:/Users/hans/Library/pnpm/nodejs/20.17.0/bin:/Users/hans/Library/pnpm:/Users/hans/.nvm/versions/node/v18.19.1/bin:/opt/homebrew/bin
KNODE=/Users/hans/.knode
NVM_BIN=/Users/hans/.nvm/versions/node/v18.19.1/bin
NVM_INC=/Users/hans/.nvm/versions/node/v18.19.1/include/node
VSCODE_INSPECTOR_OPTIONS=....
❯ which node
/Users/hans/.nvm/versions/node/v18.19.1/bin/node
I run
So, I again look at the source code for At this point, I started troubleshooting and testing different things trying to figure out how/why/when VS Code "sets" Now, I start VS Code via a Script Kit script. I have a custom script that list a set of project folders, and open the selection in VS Code (love this feature). E.g. And, ❯ printenv | grep node
NODE_PATH=/Users/hans/Library/pnpm/nodejs/20.17.0/bin/node
...
From this point onward, NODE_PATH is defined in VS Code, regardless if I open it via Script Kit or not. The workaround I landed on was a VS Code setting Thanks for reading this far :) Closing thoughts pnpm: If possible it might be safer for Script Kit to install and maintain its own dependencies, and not install them globally. Node and Environment: |
|
@hansgen wow, amazing investigation, thank you!!! 💛💛💛 I'll investigate if the pnpm install script will allow me to target a specific dir to keep it coupled with Script Kit. Q: When you say "Open vs code with Script Kit", are you using the "edit()" function and passing in a path to a project? I think I can clear the env vars... but I may need to track which env vars are set by Script Kit so I don't clear all env vars. 🤔 |
Yep, that's right, this is a simplified script // aws.ts
// Returns an array with directories for projects/git repositories
const dirs = await getDirs(['some', 'root', 'paths']); // {name: string, path: string}[]
let flags = {
code: {
name: 'Code',
shortcut: 'cmd+c',
},
finder: {
name: 'Finder',
shortcut: 'cmd+n',
},
};
const selected = await arg({
placeholder: 'Open Project:',
choices: dirs.map((dir) => ({
name: dir.name,
description: dir.path,
value: path.join(dir.path, dir.name),
})),
flags,
});
} if (flag?.finder) {
open(selected);
} else if (flag?.code) {
openCode(selected);
} else if (other conditions) {
...
} else {
openCode(selected);
}
function openCode(selected: string) {
edit(selected);
} |
|
@hansgen Does a simple hack like this fix it? function openCode(selected: string) {
delete process.env.NODE_PATH
edit(selected);
} |
|
Tried. It didn't work unfortunately. |
|
@hansgen Can you try this build: https://github.com/script-kit/app/releases/tag/v3.1.18 Also, make sure that NODE_PATH isn't set in your
|
|
Hi @johnlindquist, v3.1.18 works great. I removed I also downloaded v3.3.37 and that also works great. Many thanks for giving this attention! And sorry for the late response. |
|
@hansgen Glad to hear. Thanks for following up! |
|
@johnlindquist I haven't had any success getting Kit > 2.3.0 (incl. 3.11) running. Everything below: Macbook Pro 32GB RAM One time it opened a crash-report window, but before I could enter anything it crashed again. I am using The Volta log sais: .kenv/.env is: Installing
I attached the logs before and after installing |
|
@tiptronic please try 3.4.5 |
|
@johnlindquist sorry to say, but that didn't help much... The problem seems to be with PATH for Here's what I tried: Just running 3.4.5
The That's it for now - hopefully that helps your figuring out what's going on. And here's the console.log: |
|
@tiptronic This is the first time I've seen the error Perplexity said it's an Accessibility/permissions issue when Script Kit is requesting permission: https://www.perplexity.ai/search/what-is-this-error-JPoEOw27S.O6iD655Umetg#0 Would you be willing to try out that suggested fix? |
After upgrading MacOS to Sequoia, Kit fails to start with the following error:
[0917/222845.976752:WARNING:crash_report_exception_handler.cc(235)] UniversalExceptionRaise: (os/kern) failure (5)
Failed to initialize sandbox.[1] 7019 segmentation fault ./Kit
The computer is a MacBook Pro M3. Kit was working before upgrade.
I'm happy to provide more information or try to debug this. Let me know how I could help.
❯ ./Kit
22:28:45.624 › 📀 Stored KENV: /Users/kyen/.kenv
22:28:45.627 › Path to kitStore: /Users/kyen/Library/Application Support/Kit/config.json
22:28:45.629 › ⭐️ Other notable Kit logs: {
mainLogPath: '/Users/kyen/Library/Logs/Kit/main.log',
updateLogPath: '/Users/kyen/Library/Logs/Kit/update.log',
keymapLogPath: '/Users/kyen/Library/Logs/Kit/keymap.log'
}
22:28:45.629 ›
🟢🟢 🟢 !!!SCRIPT KIT TIME!!! 🟢 🟢 🟢
22:28:45.734 › Setting up process.env
22:28:45.747 › Appending switch: ignore-certificate-errors
22:28:45.748 › Prefs: {
appDb: {
version: '0.0.0',
openAtLogin: true,
previewScripts: true,
autoUpdate: true,
tray: true,
authorized: false,
searchDebounce: true,
termFont: 'monospace',
convertKeymap: true,
cachePrompt: true,
mini: false,
disableGpu: false,
disableBlurEffect: false
}
}
22:28:45.775 ›
Release channel: dev
Arch: arm64
Platform: darwin
Node version: v18.18.2
Node path: /Users/kyen/.knode/bin/node
Electron version: 28.1.1
Electron Node version: 18.18.2
Electron Chromium version: 120.0.6099.109
Electron execPath: /Applications/Kit.app/Contents/MacOS/Kit
[0917/222845.976752:WARNING:crash_report_exception_handler.cc(235)] UniversalExceptionRaise: (os/kern) failure (5)
Failed to initialize sandbox.[1] 7019 segmentation fault ./Kit
The text was updated successfully, but these errors were encountered: