Kap: Hide cursor not working on High Sierra 10.13.5

[equinusocio]

macOS Version: 10.13.5
Kap Version: 2.2.0

Steps to reproduce

Uncheck the show mouse cursor toggle

Current behaviour

Mouse cursor is recorded

Expected behaviour

Mouse cursor should be hidden from records

[albinekb]

Can't reproduce on 10.13.4 (17E202)

[equinusocio]

Here a gif recorded with kap

[albinekb]

I'm updating to 10.13.5 now and will see if I can reproduce and check what's up here 👍

[equinusocio]

@albinekb I noticed the same bug on Screenflow (right now). I think they changed something with 10.13.5.

[albinekb]

Must be a bug with 10.13.5 then..
https://github.com/wulkano/aperture/blob/master/swift/aperture/Recorder.swift#L34-L43
These are the lines that disables the cursor, using Apple's swift API AVCaptureScreenInput and capturesCursor 🤔

[equinusocio]

@albinekb
Maybe this link will help you. I don't know if they changed something
https://developer.apple.com/documentation/avfoundation/avcapturescreeninput/1385601-capturescursor

[albinekb]

Yeah, we're sending false to it, so maybe a bug that got introduced as part of Mojave screen capture built in? 🤔 Don't know. Need to dig deeper.

[equinusocio]

@albinekb Damn. So i need to wait Apple to fix this (hoping they will know about it :D)

PS: I can confirm it as os bug, also Principle have the same issue.

[albinekb]

I've filed a bug report with apple... Don't think there's anymore we could do here :/

[equinusocio]

@albinekb There is a public link?

[sindresorhus]

@albinekb Make sure you mirror it on https://openradar.appspot.com and paste a link here ;)

[albinekb]

https://openradar.appspot.com/radar?id=4935854782939136

[equinusocio]

@albinekb I have a bad news. With another (older) Mac with same OS version i don't have this issue (with any of the mentioned software)

[albinekb]

Can you check if it's the same build of 10.13.5? if you click the version number it should have the build ID there (in that window) @equinusocio

[equinusocio]

@albinekb Both have the 17F77 build. The only differents at this point is the mac model. The bug does not exist on mac mid 2014, but it exist on my mac 2017 with touchbar.

[albinekb]

Update from apple. Sounds like it's a known bug, and it won't be fixed in 10.13.x. Let's hope Mojave is working like it should?

[oliveratgithub]

I can test this with the recent macOS Mojave Beta release. Will post here when I did so.

Update looks fine in macOS Mojave 10.14 Beta (18A314k) using Kap version Version 2.2.0 (2.2.0.880)

[skllcrn]

Thank you @oliveratgithub!

[lacostenycoder]

Would it kill you to support older Mac OS versions? i.e. I'm Never Getting High Sierra aka 10.11.16 aka El Capitan Who Doesn't Get High lol. However I was able to get release 1.0 to work but had to block auto-updates with my firewall. NP.

[albinekb]

No, unfortunately we don't have the time to test and develop for older OS. We need to focus our efforts where it counts, as you mentioned you can continue to use 1.0 forever. Update to take advantage of the updates we provide.

[equinusocio]

I can confirm. Fixed on Mojave.

[sindresorhus]

Since this is fixed on Mojave and there's nothing we can do about High Sierra and I doubt Apple will fix it there, we should just disable the input on High Sierra and add a small note telling the user about the macOS bug.