Skip to content

fix(auth): claim Play services' identity for Google Prompt requests - #324

Merged
LisoUseInAIKyrios merged 1 commit into
MorpheApp:devfrom
rushiranpise:fix/google-prompt-identity
Oct 25, 2026
Merged

LisoUseInAIKyrios merged 1 commit into
MorpheApp:devfrom
rushiranpise:fix/google-prompt-identity

Conversation

@rushiranpise

Copy link
Copy Markdown

Google only issues the notifications token to its own package. microG asked for it as app.revanced.android.gms, a name Google has never seen, so the request was rejected as UNREGISTERED_ON_API_CONSOLE and no two-step prompt ever reached the device. Chime registration failed the same way with gRPC INVALID_ARGUMENT, because it registered that same package name.

Send com.google.android.gms for the notifications OAuth microG makes for itself, and register chime under that package. Every other internal token request still identifies as this build.

Fixes #308.

Google only issues the notifications token to its own package. microG asked
for it as app.revanced.android.gms, a name Google has never seen, so the
request was rejected as UNREGISTERED_ON_API_CONSOLE and no two-step prompt
ever reached the device. Chime registration failed the same way with gRPC
INVALID_ARGUMENT, because it registered that same package name.

Send com.google.android.gms for the notifications OAuth microG makes for
itself, and register chime under that package. Every other internal token
request still identifies as this build.

Fixes microg#308.
@LisoUseInAIKyrios
LisoUseInAIKyrios merged commit 7c7268c into MorpheApp:dev Oct 25, 2026
2 checks passed
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.

bug: Google Prompt number matching fails because outgoing requests use MicroG RE’s package name

2 participants