Run macOS runtime as the app executable#6
Merged
Conversation
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.
Summary
Stringcast.appexecutableWhy
Previously, the macOS bundle launched the Rust runtime as an embedded helper executable under
Contents/Resources/stringcast. macOS treated that helper as a separate permission identity fromStringcast.app, so users had to grant Accessibility/Input Monitoring twice.This PR fixes that by making the Rust runtime the app's main executable. The Swift menu bar component is now only a companion UI. With the rebuilt app, users should only need to grant permissions to
Stringcast.app.Verification
cargo fmt --checkcargo clippy --all-targets -- -D warningscargo testcargo build --releasepackaging/macos/build_app.sh