Hello Community and Google Cloud Engineers,
I am experiencing a critical backend synchronization issue that is completely blocking my live production application on the Google Play Store.
### Problem:
While trying to recreate an Android OAuth 2.0 client ID in my current Google Cloud project, the console immediately fails and returns the error: “Requested entity already exists”.
(Note: For security reasons, I am masking my actual production credentials below, but I can provide the exact values to a Google Cloud Engineer via private direct message if needed).
The client ID details are:
- Package Name: (My production package name)
- SHA-1 Fingerprint: (My SHA-1 fingerprint)
### Context & What I’ve Tried:
1. This specific Package/SHA-1 combination was accidentally registered in an old Google Cloud project first.
2. I have fully deleted the OAuth client from that old project’s Credentials page.
3. Despite being completely removed, the global Google Cloud infrastructure is still holding a “ghost entry” or reservation for this combination, blocking me from creating it in the correct project.
4. I also tried setting up a temporary fallback keystore with a different SHA-1, but this is not a viable workaround for production.
### Why this is urgent:
This is a live application managed via Google Play App Signing. The release SHA-1 fingerprint is tightly locked on Google’s servers. I CANNOT change the package name or generate a new production keystore without completely breaking app integrity and updates for my active users.
Since I own both accounts and projects involved, there is no security conflict. Could a Google Cloud backend engineer please look into this and perform a manual flush/cleanup? I am ready to provide my exact Project IDs, Package Name, and SHA-1 values as soon as an engineer reaches out.
Any help or escalation would be greatly appreciated as my users are currently blocked from logging in. Thank you!