What happens
When Clips does not have macOS Screen Recording permission, starting a native recording can fail later with this generic error:
native recording file missing: No such file or directory (os error 2)
Local logs show the real earlier failure is the macOS TCC denial path:
Content unavailable: The user declined TCCs for application, window, display capture
The app then falls back to /usr/sbin/screencapture, but that fallback can exit without writing the expected file. Because the fallback output is not validated immediately, the user only sees the later missing-file error.
Expected behavior
Clips should not silently fall back to screencapture when ScreenCaptureKit failed because Screen Recording permission is denied. It should surface an actionable permission error and log the fallback output failure when screencapture exits without writing a recording.
Proposed fix
Draft PR: #1651
What happens
When Clips does not have macOS Screen Recording permission, starting a native recording can fail later with this generic error:
native recording file missing: No such file or directory (os error 2)Local logs show the real earlier failure is the macOS TCC denial path:
Content unavailable: The user declined TCCs for application, window, display captureThe app then falls back to
/usr/sbin/screencapture, but that fallback can exit without writing the expected file. Because the fallback output is not validated immediately, the user only sees the later missing-file error.Expected behavior
Clips should not silently fall back to
screencapturewhen ScreenCaptureKit failed because Screen Recording permission is denied. It should surface an actionable permission error and log the fallback output failure whenscreencaptureexits without writing a recording.Proposed fix
Draft PR: #1651