feat(app-store): add sandboxed App Store scheme - #147
Merged
Conversation
esphynox
changed the title
esphynox
added
documentation
esphynox
marked this pull request as ready for review
September 6, 2026 17:12
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
Add a separate sandboxed
Keyty AppStoretarget and scheme for App Store builds. The direct-distributionKeytytarget remains on the Developer ID release path.This establishes the project and signing configuration only; App Store CI/CD and upload automation are intentionally out of scope.
Included
AppStorebuild configuration andKeyty AppStorescheme.Tests
tuist generatexcodebuild test -project Keyty.xcodeproj -scheme Keyty -destination 'platform=macOS'UI Changes
N/A
Documentation
Docs/BUILD.mdRelease Notes
N/A