Kit crashes after launching on Apple M1 Pro / Monterey 12.4 about kit HOT 34 OPEN

@MoritzBru

Try cmd+0 after the main shortcut. That will reset prompt positions in case a monitor/resolution changed where prompt positions get cached.

(My first guess is that it's appearing off-screen)

from kit.

The upcoming build has a fix where the prompt checks if it's "in-bounds" of the screen dimensions and will correct itself if not.

It should take care of these scenarios where the position caching conflicts with osx moving displays around when monitors connect/move/whatever

from kit.

I have a similar issue that the main window is not showing up.
Although when I search blindly for a script to run, this script then works: e.g. the dad jokes

I am on Monterey 12.5

from kit.

Yep! After installing patch-package globally (npm i -g patch-package if anyone's referencing this for whatever short amount of time this remains an issue), the app was able to complete the setup process:

Thanks for your help!

from kit.

@acrobertson Awesome, thanks for the communication. It's really, really appreciated! Let me know if there's anything else I can help with.

from kit.

Few things to check:

Do you see any "Kit" processes in your activity monitor?

Did it create a '~/.kit' directory?

Is there a '~/.kit/logs/kit.log'?

from kit.

I am having the same issue with the Apple Silicon, which I installed first. Then I attempted to install the Intel version. Here is my log file.

kit.log

from kit.

@cynthiateeters Thanks for the log!

Do you see the Kit icon in the menubar or any "Kit" processes running in activity monitor? The logs look like everything is set up correctly...

from kit.

Yes, here is the activity monitor:

from kit.

@cynthiateeters thx, do you see the icon in the menubar? Does the cmd+; shortcut work for you?

from kit.

I think I found it. Looks like someone pushed a change to an @octokit package which is silently causing the dependency install step to fail. I'll figure it out and lock the versions to avoid this in the future:

➜  .kit ~/.knode/bin/npm i
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: @johnlindquist/[email protected]
npm ERR! Found: @octokit/[email protected]
npm ERR! node_modules/@octokit/core
npm ERR!   @octokit/core@"^3.6.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @octokit/core@">=4" from @octokit/[email protected]
npm ERR! node_modules/@octokit/plugin-paginate-rest
npm ERR!   @octokit/plugin-paginate-rest@"^2.17.0" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /Users/johnlindquist/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/johnlindquist/.npm/_logs/2022-07-09T04_08_34_221Z-debug-0.log

I'll get it sorted tonight and push out another build ASAP.

from kit.

Thanks!! 😄

from kit.

@cynthiateeters If you'd like to fix it or just curious:

1. Open ~/.kit/package.json, a remove the ^ from this line:

Before:

"@octokit/plugin-paginate-rest": "^2.17.0",

After:

"@octokit/plugin-paginate-rest": "2.17.0",

(You can see in their releases that they pushed a 2.x.x version which updated to @octokit/core v4 which is what's breaking our install since we have a @octokit/core at v3)

2. Terminate any Kit processes in activity monitor.

3. Install the packages in the terminal

cd ~/.kit && ~/.knode/bin/npm i

4. Then re-open Kit.app and everything should work fine.

(I'm working on the pushing the fix tonight regardless)

from kit.

Alright, I pushed out the new build on scriptkit.com. It the auto-updater might still work, but if not, here's direct links for convenience.

(Please make sure to end and running Kit processes before starting the new install)

m1: https://github.com/johnlindquist/kitapp/releases/download/v1.20.5/Kit-1.20.5-arm64.dmg
Intel: https://github.com/johnlindquist/kitapp/releases/download/v1.20.5/Kit-1.20.5.dmg

Thanks again for bringing this to my attention. The versions are locked now, so this type of error shouldn't ever happen again.

from kit.

I had to get rid of everything that was previously there before the new install. It's working. Thanks!

from kit.

Guess I called success too soon. I tried the Dad Joke example. I got a joke read to me and then the window disappeared and I can't get it to come back.

kit.log

from kit.

@cynthiateeters Hmm, that log looks fine.

1. Can you post this log? ~/Library/Logs/Kit/main.log
2. Is the menubar icon still visible?
3. Are there any "Kit" processes running in the activity monitor?

from kit.

main.log

from kit.

Menu bar icon is visible

from kit.

from kit.

If you run:

tail -f ~/.kit/logs/kit.log

Then hit cmd+; or Open Kit.app prompt

Do you see the kit.log updating?

from kit.

OK, maybe I didn't understand how this works. The kit window disappears if I do anything else and will not reappear when I click on the icon in the menu bar.

It does, though, reappear when I hit cmd+;.

If this is wanted behavior, I can live with that.

from kit.

Do you see this menu when click on the icon in the menubar? The first option "Open Kit.app prompt" should open the main window again. If not, then something's broken...

from kit.

No, I do not see that come up.

from kit.

1. Which osx version are you on?
2. Are you using multiple monitors?

I'm having trouble reproducing 🤔

from kit.

from kit.

Sorry I am very slow to reply. Yes, I have multiple monitors.

from kit.

@johnlindquist same happend to me just now.

it feels like it has something to do with my 2nd screen. scriptKit did not 'not' show up when no 2nd screen attached.
after clicking the scriptKit icon and then hitting cmd+0, scriptKit appeared again. closing the scriptKit and triggering scriptKit with cmd-; worked again.

from kit.

I'm experiencing the same issue @jmlivingston originally reported.

Steps I've taken so far:

1. Install Silicon build (v1.20.5) from the site. (I'm on Monterey 12.6, and I have never installed Script Kit on this machine before.)
2. Copy Kit into Applications.
3. Open Kit.
4. Splash screen appears, makes it to updating ~/.kit packages... and then crashes before I can fill out the form. (This happens every I open the app.)

Notes to address questions raised in previous comments:

• I was initially on an external monitor, but after reading the previous comments I tried it without any monitors plugged in and experienced the same issue.
• While the splash screen is visible, the icon appears in the menu bar and Kit processes are visible in Activity Monitor. When the window closes, everything goes away.
• I do have a ~.kit directory now. (It seems to be re-created every time I open the app.)

Here's my log file:

main.log

This seems to be the relevant portion (repeated for every open attempt):

[2022-09-23 15:47:35.356] [warn] Error: Install not verified...
    at /Applications/Kit.app/Contents/Resources/app.asar/main.prod.js:2:232959
    at tryCatch (/Applications/Kit.app/Contents/Resources/app.asar/node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:63:40)
    at Generator.invoke [as _invoke] (/Applications/Kit.app/Contents/Resources/app.asar/node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:294:22)
    at Generator.next (/Applications/Kit.app/Contents/Resources/app.asar/node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:119:21)
    at sc (/Applications/Kit.app/Contents/Resources/app.asar/main.prod.js:2:218059)
    at a (/Applications/Kit.app/Contents/Resources/app.asar/main.prod.js:2:218263)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
[2022-09-23 15:47:35.378] [info] Hiding because undefined

This sounds almost like a macOS security issue? Do I need to grant privileges to it somewhere in System Preferences? But I can't tell from the log whether the "install" in question is the Kit app or my OS, or where the error is coming from. Hopefully you have more insight there! Let me know if you need me to provide additional details.

from kit.

@acrobertson thanks for the log, looks like

{ npmResult: 'Deps install exit code 127' }

is the important bit.

Does ~/.knode/bin/ exist on your machine? I think it's failing because it can't find ~/.knode/bin/npm to install the packages in ~/.kit

from kit.

Ah, interesting! Sidenote: immediately after posting I realized I hadn't searched the Discussions (sorry about that) and found this post there with the same issue. But the suggested scripts didn't work for me because I don't have a ~/.kit/node directory. Was that moved to ~/.knode?

Regardless, I do actually have a ~/.knode/bin/npm, which I guess is strange.

Do I need to edit my $PATH? I don't see it in there.

from kit.

@acrobertson

No, you shouldn't need to edit your $PATH, Script Kit should set temp paths internally.

Hmm, does this throw any errors?

(This is manually doing the step the app attempts during startup)

cd ~/.kit
PATH=~/.knode/bin:$PATH npm i

from kit.

@johnlindquist

It does, but probably not one you expected!

It appears that underscore is trying to run a post-install script with patch-package, which I don't have installed.

Checked their repo, and found this issue (among others) reporting it.

Seems like that's the real issue here.

from kit.

@acrobertson Crap, I made the mistake of not locking versions in ~/.kit, I won't make that mistake again...

Does the app open ok now?

from kit.