Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

[Bug]: macOS Accessibility warning persists after permission is enabled

Offen
  • Stimmt etwas nicht?
#1,196 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
Ein halber Tag
Anfängerfreundlichkeit
50/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
electron, macos, typescript
Bereich
desktop

Rechercherichtung

Start in src/hooks/useScreenRecorder.ts, where the darwin editable-overlay preflight calls requestNativeMacCursorAccess and shows recording.cursorAccessibilityUnavailable on a not-determined helper result. The proposed change removes that toast and the System Settings prompt, keeping the position-only fallback. Done means a regression test shows recording starts without the Accessibility toast, and the change is checked on a macOS build.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Search existing issues
  • I have searched the existing issues
  • Related: #878 and merged fix #886
Describe the bug

On macOS, OpenScreen can still show the Accessibility warning even after Accessibility is enabled for the OpenScreen app in System Settings.

Observed message:

Accessibility is off. Recording will continue, but cursor effects may be limited. Enable it in System Settings for full cursor effects.

The warning is misleading in this state: the main app is authorized, recording can start, and the warning appears to be based on the result of a separate native cursor helper process rather than the main OpenScreen app's TCC grant.

This was first observed in a local 2.0.1-hans.7 build and reproduced in a local arm64 build based on the official v2.0.0 code line. I have not yet claimed that it reproduces in the unmodified notarized v2.0.0 DMG.

Expected behavior
  • Accessibility should be treated as optional for recording.
  • If the main app is authorized, no Accessibility warning should be shown.
  • If Accessibility is unavailable, recording should still start with position-only cursor telemetry, without repeatedly opening System Settings.
  • A warning should only be shown when the app can reliably determine that the main app's permission is missing.
To Reproduce
  1. On macOS, enable OpenScreen under System Settings → Privacy & Security → Accessibility.
  2. Restart OpenScreen.
  3. Use the cursor/editable-overlay recording mode.
  4. Start a recording.
  5. Observe that the Accessibility warning can still appear even though the permission is enabled.
  6. The recording itself can still succeed.
Environment
  • OS: macOS 26.6.2
  • Architecture: Apple Silicon (arm64)
  • Official release line: v2.0.0
  • Bundle identifier: com.etiennelescot.openscreen
Proposed fix

Treat the native cursor-access request as best-effort and do not use its helper-process status as a recording-start gate or as proof that the main app lacks Accessibility.

In src/hooks/useScreenRecorder.ts, the recording preflight can be reduced to:

if (platform === "darwin" && cursorCaptureMode === "editable-overlay") {
  await window.electronAPI.requestNativeMacCursorAccess();
}

Remove the recording-start path that:

  • tracks cursorAccessibilityWarningShown;
  • shows recording.cursorAccessibilityUnavailable based on a not-determined helper result;
  • opens System Settings from that toast.

Keep the native cursor session's position-only fallback and add a regression test asserting that recording starts and the misleading Accessibility toast is not shown.

I applied this change locally. Targeted tests passed, and a real 87.9-second H.264/AAC recording completed successfully.

Separate packaging note

During local testing, an ad-hoc package whose main executable identifier was Electron produced SCStream -3805 (application connection interrupted). Restoring the official bundle identifier com.etiennelescot.openscreen and preserving the correct app identity removed that failure. This appears to be a local packaging/signing issue rather than an upstream runtime regression, but the release packaging should continue to preserve the app bundle identity.

Vorherrschende Sprache
TypeScript
Sterne
3.7k
Forks
231
Ø Merge
16 Std. 25 Min.
Gemergte PRs (30 T.)
331

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus getopenscreen/openscreen

Alle Issues in getopenscreen/openscreen

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.