-
Notifications
You must be signed in to change notification settings - Fork 827
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
Contributing – running app locally by yarn start, but I can't allow recording permissions in the development #1207
Comments
I am running into the same issue. The Kap app is listed and allowed for screen capturing but that does not help when running the dev script. |
Maybe it has something to do with the older version of the "mac-screen-capture-permissions" package that is used. Or the missing application signing? Even if I create a production build and manually assign the screen recording permission to that specific build, its asking again for the same permissions. |
Same problem here. But on a positive note for Kap, I now realize how solid of a product this is. Like tp, you only notice its value when you don't have it 😉 . Have to use Quicktime and Adobe Encoder to achieve similar results and take 4x the amount of time. |
Update on the above comment, I just updated my mac OS, and it's back to working fine. So it was the problem with the toilet after all, not the tp |
And it seems that the performance issue on MacOS Sonoma 14.4 is a bit less noticeable. Before Kap was unusable whereas it is usable now (with a bit of patience tough). I did not have a chance to test the DEV permission problem yet. |
see this #1231 |
macOS version: 14.0
Kap version: 3.6
Steps to reproduce
Follow https://github.com/wulkano/Kap/blob/main/contributing.md and run "yarn start"
Current behaviour
Once I click "Open System Preferences" there is no Kap / Kap Development in the list of apps in the screen recording permission settings.Expected behaviour
A way to run Kap from the source locally in the development mode.
Workaround
The text was updated successfully, but these errors were encountered: