Hello Google Cloud Security Community,
I am seeking guidance on recovering an existing Android OAuth 2.0 client registration for Rimbers, a published Android application operated under Damac Hills Company.
Application details:
-
Application: Rimbers
-
Android package name: com.damac.rimber
-
Authentication: Flutter Google Sign-In with Supabase Auth
-
Current Google Cloud project: versatile-skein-508811-v6
-
Historical Google Cloud project number: [removed by moderator] (possible connection, not confirmed)
Problem:
Google Sign-In fails in our published Android application with unknownError [28444] before obtaining the Google ID token.
When attempting to register the existing Android package name and Google Play app-signing SHA-1 in our current Google Cloud project, Google returns:
"The request failed because the Android package name and fingerprint are already in use."
This suggests the package name and certificate fingerprint are already registered in another Google Cloud project, potentially controlled by the original developer.
We do not have access to the original developer's Google account.
Our questions:
-
Is there an official process for identifying or recovering an Android OAuth registration associated with an inaccessible Google Cloud project?
-
Can Google verify Google Play Console ownership and help resolve the duplicate registration?
-
Is there a supported way to migrate or release the Android OAuth registration without changing the published application's package name or signing certificate?
-
Which Google support or escalation channel handles this type of OAuth ownership conflict?
We can provide Google Play Console ownership evidence and the official signing certificate fingerprints through an appropriate private support channel.
We want to preserve the existing published application, its signing identity, and working iOS Google Sign-In.
Thank you for any guidance.
