-
Notifications
You must be signed in to change notification settings - Fork 831
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kap is not working in the latest MacOS version #1063
Comments
Same |
Same. |
Suddenly |
Downgraded to v3.4.2. It seems to work fine. |
Downgrading was a bit irritating for me, because it kept asking for permissions it had over and over, but finally it worked. |
Why is it when I click download on the web page, it's automatically downloading the arm64 version? I'm running 12.1 beta, but on an Intel Mac. |
Same here. |
@SidKH Works well. Thanks |
Any update on a fix? |
Any progress ? |
It's still not running. I miss Kap. |
Using the version https://github.com/wulkano/Kap/releases/tag/v3.4.2 works fine. You can still use it and wait for a fix for the latest version. Let's be patient!! |
I deleted an older version because it was broken, and i can't reinstall - not even the 3.4.2 version😭 Super bummed 😭 I really miss it and I can't even find an alternative that i like. You've made a really cool product! Would be happy to pay for it. EDIT: after looking around, i found apparently right clicking on "open" will override this and let you open it even if you're getting that error. I then had to do a little dance with system preferences and permissions but i think i have eventually got it working now. Just in case that helps anyone else. |
@brittanyjoiner15 when you get the error above, try these steps:
|
@klonos yep it appears that does work! thanks for sharing that! |
Getting this error as well with Kap 3.5.1 on macos 12.0.1. I really want Kap to work and I have a question about using an older version. Currently Kap installed w brew and auto updates on, but older versions are not available in brew. Thanks! |
Hi @alechko , Please remove the one you installed with brew and then install the version mentioned here by downloading it. Hope this helps! |
@jgonzalezalbisu thanks! I will do that |
Multiple issues have been filed about that problem here. Look a bit around, in one of those threads someone has posted how to force brew to use a working version. |
Just want to mention/clarify a few things since I tried following this thread: I tried the latest version of Kap (3.5.1) and it had this error.
After downloading and you keep seeing the
Now it works great. Thanks for making an awesome tool, it has helped me out a lot! |
Can you try out the latest version? https://github.com/wulkano/Kap/releases/tag/v3.5.2 |
Sentry issue: KAP-B8E |
3.5.2 didn't work for me (Apple M1, macOS 12.1) |
@sindresorhus It didn't work for me either. System specs 👇 |
3.5.2 is working for me on macOS 12.1, Apple M1. 16" M1X |
3.5.2 is not working properly for me on macOS 12.0.1 macbook pro intel i7 it recorded once on the first launch after upgrading from 3.4.2 but then the same error appeared on second record attempt. not sure if related, but the 3.5.* versions are super slow compared to 3.4.2, almost unresponsive. between triggering kap either from taskbar or by keyboard shortcut there's a delay of few seconds followed by a loading mouse icon for another few seconds and then the selection window appears with the floating menu.
Edit: not working on macOS 12.1 as well |
Error: Could not start recording within 5 seconds Model Name: MacBook Pro |
Hi guys, I'm getting the same error. I installed version 3.4.0, but then it automatically updated 😬 Anyone know how to disable that while the new version is broken? |
Downgrading to 3.4.2 fixed most of the issues I've been having (including the extremely sluggish performance of 3.5.2) I had to manually approve the new (old) version in the MacOS "Security & Privacy" preferences. I also needed to revoke and re-grant Screen Recording permissions (also in the Security preferences). I'm guessing the version downgrade somehow confused MacOS. |
Both of |
Any update? 🙁 |
This has been resolved for a few months now with version 3.5.4 which works totally fine on Apple Silicon (my system is a MacBook Pro M1 16-inch 2021 with Generation 1 chip). |
@fers4t yes it works again tho still with huge initial lags. I doubt that is related. |
Hi all, just wondering if anyone is still seeing this error? I know about the performance issues, but wondering about the error initially noted in this issue. |
@timothyis except for being a bit slow on my intel mbp had no issues and didn't seen the error since upgrading to 3.6.0 |
Love the app, thanks so much. Getting this error when installing on M2 Max, 32GB on Ventura 13.0: Unhandled Promise Rejection |
I have the same issue with Apple M1 Pro sw, 13.6.1 (22G313) with Kap-3.6.0-arm64 error: Recording error |
This comment was marked as resolved.
This comment was marked as resolved.
source of the problem is that the node module mac-screen-capture-permissions is an intel only binary (screen-capture-permissions: Mach-O 64-bit executable x86_64), and you most probably don't have rosetta installed. It would be great if someone could do a proper Apple Silicon native build of kap (including the node modules), or a proper universal binary (including node modules)... although in this case it looks like the problem might be in the mac-screen-capture-permissions dependency iteself :/ |
I just tried building it from source with changed version of mac-screen-capture-permissions from 1.1.0 to 2.1.0 and after yarn dist it appears to work just fine (although I tried only recording one whole screen recording, so maybe more testing should be done before that is accepted as a solution to this problem) |
Check this #1231, I have addressed the intel dependency issue. Rosetta is no longer required. |
Recording error
Error: Could not start recording within 5 seconds
at Timeout._onTimeout (/Applications/Kap.app/Contents/Resources/app.asar/node_modules/aperture/index.js:132:19)
The text was updated successfully, but these errors were encountered: