Fix the issue requiring a security verification flow for in-app subscriptions#3507
Merged
Merged
Conversation
Member
|
Can we do this without changing gradle and wire versions? |
Contributor
Author
No. Older versions of Wire have a bug where Wire fails to parse protobuf data when there are very large field numbers (e.g., 268435456). Some of the field numbers defined in our proto files exceed this value, which causes the data to fail to parse. However, newer versions of Wire have fixed this issue. |
Bypasses AAPT bug
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.
Fix the issue where in-app subscriptions require going through a security authentication page (e.g., YouTube in some European regions)