Recording error

[s-seltenreich]

Sentry Issue: KAP-B8E

macOS version: Monterey (12) Kap version: 3.5.1

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)

[andreezy777]

The same problem, Looking that the 3.4.2 latest stable release for intel mac

[filfreire]

Same issue, Version 3.5.1 (3.5.1.1783) macOS 12.0.1 (21A559), MacBook Pro (16-inch, 2019)

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)

[cgilroy]

Same here, Version 3.5.1 (3.5.1.1783) macOS 12.0.1 MacBook Pro (16 inch, 2019)

[EvHaus]

Same issue here as well, but what's interested is if I restart my computer then the first recording works, but after that it breaks again.

[mbukh]

Same here Monterey 12.0.1 MacBook Pro 16" i9 (2019)

[CeciliaChiang]

Same here, Version 3.5.1 (3.5.1.1783) Big Sur 11.5.2 MacBook Pro (15-inch, 2018)

[holographicleah]

Seeing this as well, Version 3.5.1 (3.5.1.1783). Using macOS Big Sur 11.5.2, Macbook Pro (13in, 2020)

[libbyrobinson]

Same issue, 3.5.1.1783, running MacBook Pro (15-inch, 2019) on Big Sur 11.6. Works first time after restart, then won't record.

[Serko-Egor]

Same issue

[soar]

The app is totally broken

[x029a]

Same, using this often for work. Seeking alternatives now. I've noticed Kap has been running slower and slower anyway. Great app, but seems to have been getting worse.

[finn-ds]

following...

[joergRossdeutscher]

Might be related to BigSur update. I have the issue since updating yesterday.

[ITSjwags]

Also just started seeing this after upgrading to macOS Monterey.

[mojason-81]

Haven't ran any updates on my mac lately. Seeing the same issue. Was working fine just a few days ago.

[lesliemilitante]

KAP works fine a few days ago then it crashes now.

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)

[Aaaaash]

Same problem, on my Intel MAC (3.5.0), KAP can only record once, and the second time will be breaks. 😭 but it worked fine on my M1 MAC (3.4.2)

Same issue here as well, but what's interested is if I restart my computer then the first recording works, but after that it breaks again.

[Aaaaash]

Seems to have something to do with the Electron version update (Electron 12+ and macOS Big Sur)

child_process spawn locks up renderer for 300 - 3000ms on signed app on macOS Big Sur

The interim solution was to use version 3.4.2 on Intel Mac Download Kap-3.4.2

[John60676]

Seems to have something to do with the Electron version update (Electron 12+ and macOS Big Sur)

child_process spawn locks up renderer for 300 - 3000ms on signed app on macOS Big Sur

The interim solution was to use version 3.4.2 on Intel Mac Download Kap-3.4.2

thanks, it work for me.

[davidcalhoun]

Having the same issue here with Kap 3.5.1 running on macOS 11.6 Big Sur. Note that it's temporarily fixed after restarting the system, then seems to work for the first capture but breaks again after that.

Thank you @Aaaaash, downgrading to 3.4.2 is a working workaround for now for me.

[CeciliaChiang]

Seems to have something to do with the Electron version update (Electron 12+ and macOS Big Sur)

child_process spawn locks up renderer for 300 - 3000ms on signed app on macOS Big Sur

The interim solution was to use version 3.4.2 on Intel Mac Download Kap-3.4.2

Thanks a lot @Aaaaash , it works😊

[rajohns08]

Same issue here on Kap 3.5.1 and macOS 11.6.1 (Intel mac)

[soar]

Workaround (downgrading) for Brew users:

brew uninstall kap
brew tap-new local/homebrew-cask
mkdir "$(brew --repository local/homebrew-cask)/Casks"
wget "https://raw.githubusercontent.com/Homebrew/homebrew-cask/a6998a002502ecdd0c111c99964069dca3bc5df3/Casks/kap.rb" -O "$(brew --repository local/homebrew-cask)/Casks/kap.rb"
brew install local/homebrew-cask/kap

[joergRossdeutscher]

If I understand this correctly, this is not a fix, but just a downgrade to 3.4.2

(Don't want to critizise that, thanks for the work, just mentioning: Those users who, like me, think this leads to a pre-released fixed beta-something: No, it doesn't. It's just the old package). Please correct me if I'm wrong.

[soar]

If I understand this correctly, this is not a fix, but just a downgrade to 3.4.2

(Don't want to critizise that, thanks for the work, just mentioning: Those users who, like me, think this leads to a pre-released fixed beta-something: No, it doesn't. It's just the old package). Please correct me if I'm wrong.

Sure, I fixed the description. It's just downgrading via Brew. Not trivial for me, I thought it can be helpful.

[andreezy777]

Why no one admit that 17 days ago I have already wrote that 3.4.2 is stable version?

https://github.com/wulkano/Kap/issues/1059#issuecomment-990862313

brrrr...

[timothyis]

Apologies all, we are working on this.

[karuppiah7890]

I'm getting an error now too -

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)

---

Kap Version 3.5.2 (3.5.2.1799)

MacOS Version 12.1 (21C52) Monterey . Intel processor Mac

---

Downgrading to v3.4.2 helped ! :)

[msgongora]

Confirming this is happening in big sur also, 3.5.2 downgrading to 3.4.2

cd $(brew --repo homebrew/cask)
git checkout a6998a00 -- Casks/kap.rb
HOMEBREW_NO_AUTO_UPDATE=1 brew reinstall kap

[jadedrakerider]

I'm also getting this. It seems to be happening when I have Vysor running. I was able to successfully record earlier today.

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)

[ionajosephine]

I tried downloading 3.4.2 but got the error: “Kap” can’t be opened because Apple cannot check it for malicious software.

[ericclemmons]

@ionajosephine per https://issuehunt.io/r/wulkano/kap/issues/1044, you can fix that error by running:

xattr -d com.apple.quarantine /Applications/Kap.app

[steveharman]

Still happening on 3.5.2. macOS 12.2

[steveharman]

I tried downloading 3.4.2 but got the error: “Kap” can’t be opened because Apple cannot check it for malicious software.

Ctrl-click / right-click on the Kap app > Open. This is a common Apple security issue, not a Kap bug.

You may need to re-establish screen recording & other permissions in System Preferences when asked. I got into a loop of continuously being asked to grant a permission which already existed - the fix on my side was to remove the permission, quit Kap, re-launch it & re-grant the permission(s).

Again, seen that plenty of times on other apps - not a Kap issue as such.

Kap 3.4.2 seems to be ok for me on macOS 12.2, where 3.5.2 would crash each time I tried to create a recording.

[pederjohnsen]

Downgrading to 3.4.2 works thanks, would be nice if latest version would work though 😬

[StrawbunnyDev]

Having this issue too for intel mac. 3.5.2 seems to be extremely laggy. Downgraded to 3.4.2 and now it's working smoothly.

[shiftkey]

Just wanted to mention that the new 3.5.3 build seems to have resolved this for me on Intel Mac Big Sur

[timothyis]

Thanks @shiftkey! Can anyone else confirm the latest has fixed the issue?

[pederjohnsen]

@timothyis 3.5.3 intel version seems to be working now, all though pretty slow at opening 🤔

After clicking the Kap icon in the status bar it takes nearly 10 seconds before the recording UI is shown 😬

[StrawbunnyDev]

Thanks @shiftkey! Can anyone else confirm the latest has fixed the issue?

Can confirm. Running 3.5.3 Intel version has fixed this. Although after pressing on the record button, it takes about 5 seconds til it actually records.

[arihid]

This bug still present in 3.5.4 Intel version when trying to record windowed region. Fullscreen record work just fine. There are +-5s delay before the record. I don't know if this is a feature or a bug. But if this is a feature, adding an actual timer would make sense imo.