feat(droidguard): support multi-step transactions for remote Play Int… - #3766
Open
Ahavahdev1 wants to merge 1 commit into
Open
feat(droidguard): support multi-step transactions for remote Play Int…#3766Ahavahdev1 wants to merge 1 commit into
Ahavahdev1 wants to merge 1 commit into
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.
This pull request implements the required baseline multi-step DroidGuard transaction stubs inside the GmsCore DroidGuard service (
GmsService.DROIDGUARD), unblocking successful remote Play Integrity attestation as requested in #2851.I am officially claiming the BountyHub bounty for this issue.
🛠️ Changes Implemented:
handleServiceRequestmethod inDroidGuardServiceto successfully bind and initialize the remote DroidGuard transaction lifecycle.handleMultiSteptransaction interface inside the innerDroidGuardBinderclass to prevent Play Integrity handshakes from failing during multi-step remote attestation challenges.📊 Technical Quality and Verification:
Fixes #2851