Skip to content

Bump gmsVersion to 25.19.31#3361

Open
opstic wants to merge 1 commit intomicrog:masterfrom
opstic:bump-version
Open

Bump gmsVersion to 25.19.31#3361
opstic wants to merge 1 commit intomicrog:masterfrom
opstic:bump-version

Conversation

@opstic
Copy link

@opstic opstic commented Mar 24, 2026

This is PR 3 of 3 towards RCS support.
Related PRs: #3359, #3360
Related issue: #2994

Collectively these changes enable Google Messages to verify the phone number via UPI and retrieve the provisioning document.

In my testing, setup progresses through verification, provisioning and reaches a connected state in Google Messages.
The remaining failure occurs during Tachyon registration. One possible cause is that the final DroidGuard tachyon_registration challenge is not being satisfied correctly in my test environment.

Testing from people with environments that pass DroidGuard/Play Integrity would be appreciated, especially with logs/network captures if possible. Many thanks!

Description

This PR bumps the spoofed gmsVersion to 25.19.31.

By using a script that patches the reported com.google.android.gms version in the request payload and performs a binary search, I determined that mobileconfiguration-pa.googleapis.com only begins dispatching UPI-enabled configurations when the reported GMS version is ≥ 25.19.00.

25.19.31 was chosen as the smallest bump above this threshold that corresponds to an actual released version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant