Dev: use build product flavors for app store release#1205
Merged
damontecres merged 5 commits intomainfrom Apr 6, 2026
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.
Description
Instead of applying a code patch, this PR uses build time product flavors to define the existing default and an app store variant. This is more robust than maintaining a patch file and making sure it is applied before building.
The app store variant applies the same code changes (removing install permission, requiring leanback, & setting
UpdateChecker.ACTIVE), but via manifest placeholders/merging andBuildConfigentries.There are no user facing changes.
Related issues
None
Testing
Built the variants and verified manifest changes via aapt
Screenshots
N/A
AI or LLM usage
None