Skip to content

feat(permissions): use target-specific input access - #158

Merged
esphynox merged 12 commits into
mainfrom
feat/input-monitoring-permission
Sep 14, 2026
Merged

esphynox merged 12 commits into
mainfrom
feat/input-monitoring-permission

Conversation

@esphynox

@esphynox esphynox commented Sep 14, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Use Input Monitoring exclusively in App Store builds and Accessibility exclusively in non-App-Store builds.
  • Update input capture, Settings, onboarding, deep links, and badge counts to use the required permission for the active target.
  • Document the target-specific setup and recovery steps.

Tests

  • tuist generate
  • xcodebuild test -project Keyty.xcodeproj -scheme Keyty -destination 'platform=macOS'
  • Other: built Keyty (Debug) and Keyty AppStore (AppStore); ran 29 focused permission and capture tests.

Run project commands from Apps/Keyty.

UI Changes

Permissions Settings and onboarding now display only the one permission required by the active target; the sidebar badge reports at most one missing permission.

Non App-Store App Store
Screenshot 2026-09-14 at 12 28 37 Screenshot 2026-09-14 at 12 28 18

Documentation

  • Updated relevant docs
  • No docs needed

Release Notes

App Store builds now request Input Monitoring, while non-App-Store builds request Accessibility. The Permissions interface shows only the permission required by the active build.

@esphynox esphynox added the enhancement New feature or request label Sep 14, 2026
@esphynox
esphynox merged commit 9fc31d1 into main Sep 14, 2026
1 check passed
@esphynox
esphynox deleted the feat/input-monitoring-permission branch September 14, 2026 10:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant