Repository navigation
fix(ml): preserve Flogger and protobuf metadata in R8 release builds - #13
Merged
raulshma merged 1 commit intoOct 27, 2026
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
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
Fixes MediaPipe object detection failing to initialize in R8-optimized release builds of LensCast v0.1.7.
The fix preserves Google Flogger's stack-based caller lookup and protobuf fields accessed through reflection by adding keep rules to
app/proguard-rules.pro.Root cause
The original release failed with:
Preserving Flogger resolved the first error but exposed a second:
Adding the protobuf keep rule resolved this failure.
Verification
Tested on a Samsung Galaxy S10+ running Android 12:
personlabels.The protobuf rule is intentionally conservative and could be narrowed with further regression testing.
Fixes #12