Contributing – running app locally by yarn start, but I can't allow recording permissions in the development

[pawelkontek]

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

[michaeleichmann]

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.

[michaeleichmann]

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.

[amikhail006]

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.

[amikhail006]

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

[michaeleichmann]

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.

[chrispestcode]

I'm on v3.6.0 and ran into the same issue with launching Kap with yarn start on MacOS Sonoma.

Two things:

1. I allowed permissions for Screen & System Audio Recording for the Terminal.

2. When launching, I received a notification for allowing Electron to accept incoming network traffic. Once I accepted, I was able to launch the application.

[codercodingthecode]

see this #1231