Repository navigation
fix: enable Android release code obfuscation and resource shrinking - #762
Merged
Merged
Conversation
Contributor
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
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.
Google Play reports only 1% DEX obfuscation for release 3.2.0. Enable Android release minification through
expo-build-propertiesso R8 can shrink and obfuscate native code, and enable unused-resource shrinking. These settings apply to release builds, including preview builds used for validation.Validation: Expo config introspection confirms both generated Android Gradle properties are
true;git diff --checkpasses. An Android release build and device smoke test are still needed before publishing, and the resulting Play optimization percentage has not been measured. The separate edge-to-edge dependency warning is not resolved by this change.