Onboarding: open the Accessibility pane directly#2
Merged
Conversation
macOS suppresses the Accessibility consent alert for sandboxed apps, so a button that only calls AXIsProcessTrustedWithOptions appears to do nothing. Open the Privacy & Security → Accessibility pane from the button instead, and reword the onboarding copy for the manual flow (enable Fit in the list, + to add it if missing). The trusted-check call stays so Fit registers itself in that list. Update the review-notes template and BUILDING.md to describe the same manual flow — App Review will hit the exact same behavior. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Real-device verification showed that with the sandbox enabled, AX writes to other apps' windows fail even after the user grants Accessibility permission — every snap action dies with a beep. The existing Mac App Store window managers (checked Magnet's entitlements on-device: no com.apple.security.app-sandbox) are non-sandboxed apps grandfathered from before the 2012 sandbox mandate, not proof that sandboxed AX control works. New apps in this category cannot ship on the Mac App Store; docs/APPSTORE.ja.md now records that finding and lays out the Developer ID + notarization + external-payment route instead. Keeps from the App Store work: PrivacyInfo.xcprivacy, version 1.0, and the onboarding button opening the Accessibility pane directly (the consent alert never reappears after a rebuild, so the pane is the reliable path regardless of sandboxing). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
macOS suppresses the Accessibility consent alert for sandboxed apps, so a button that only calls AXIsProcessTrustedWithOptions appears to do nothing. Open the Privacy & Security → Accessibility pane from the button instead, and reword the onboarding copy for the manual flow (enable Fit in the list, + to add it if missing). The trusted-check call stays so Fit registers itself in that list.
Update the review-notes template and BUILDING.md to describe the same manual flow — App Review will hit the exact same behavior.
What & why
Checklist
swift testpassesWindowing/orInput/changedREADME.md/README.ja.md/docs/DESIGN.ja.md) if behavior or architecture changed