🐛 Fix not precise ProGuard rules regarding Flutter classes which lead to build failure#151
Open
AlexV525 wants to merge 1 commit into
Open
🐛 Fix not precise ProGuard rules regarding Flutter classes which lead to build failure#151AlexV525 wants to merge 1 commit into
AlexV525 wants to merge 1 commit into
Conversation
… to build failure
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
2 participants
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.
Fixes sensorsdata/sensors_analytics_flutter_plugin#39
When keeping all classes under
io.flutter.embedding.engineandio.flutter.embedding.android, the split application and deferred components feature will require havingcom.google.android.play.coredependency, leading to unexpected build failure and making it hard to find the root cause.We only need these rules since the code reflects them. Consider adding more scopes only after further business development.