I am trying to create a new app in Google Play Console with the package name:

com.oopsable.clipcode

During Android Developer Verification, Play Console asks me to select an eligible public key instead of allowing me to add a new one.

The only eligible SHA-256 fingerprint shown is my debug key fingerprint.

After investigating, I found that this debug SHA-256 was already added earlier in Firebase Authentication for the same package name, which is probably why Google associated the package with the debug certificate.

My issue is that I want to use my release keystore for production.

What I already tried:

• Generated a proper release keystore

• Added both release SHA-1 and SHA-256 fingerprints to the same Firebase Android app

• Built a release APK signed with the release keystore

• Installed the release APK on a real Android device

• Opened and used the app

• Waited more than 24 hours

However, the Play Console still only shows the debug SHA-256 fingerprint under eligible keys, and the release SHA-256 never appears.

I also found this related discussion:
<https://stackoverflow.com/questions/79929259/play-console-only-shows-debug-sha-256-key-when-registering-package-name-not-rel>

Some comments suggest that installing a release-signed APK may eventually make the release SHA appear, but that has not happened in my case.

My questions:

1. Is there any reliable way to force Play Console to recognize the release SHA-256 fingerprint?

2. Does Play Console cache eligible keys permanently once a package gets associated with a debug key?

3. If I complete verification using the debug key, can I still safely use my release keystore later for production uploads with Play App Signing?

4. Has anyone successfully resolved this without changing the package name?

Any help would be appreciated.