Update advertisement encoding logic to use the Rust NP library #2625
Conversation
This file contains 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
![copybara-service[bot]](https://github.com/avatars/in/44061?s=60&v=4){kind=small}
By doing so updates the created advertisement format to match whats in the latest NP Specification which makes them compatible with the GmsCore implementation. Also updates naming of variables in the proto to match the current spec, ie metadata_encryption_key -> identity_token PiperOrigin-RevId: 635579714
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.
Update advertisement encoding logic to use the Rust NP library
By doing so updates the created advertisement format to match whats in the latest NP Specification which makes them compatible with the GmsCore implementation.
Also updates naming of variables in the proto to match the current spec, ie metadata_encryption_key -> identity_token