Hi, Andy:
So the Firebase project is a Google project, if you have the same app name and SHA-1 in the Firebase (i.e., Google Cloud) project and your GCP project, it's technically in two Google Cloud projects and the app bundle name + SHA-1 must be unique across all Cloud projects. Now, you
can have the same app bundle name in two different projects,
but you can't use the same SHA-1 in combination with that app bundle name in both projects.
However, if you're just using this for Google Sign-in, you could retain the OAuth2 client in your Play-specific project, remove the SHA-1 fingerprint from the app in the Firebase project, and then safelist the Play project's OAuth2 client ID in your dev Firebase project (note that you wouldn't want to remove the fingerprint from an app in production). This blog post is from a while back, but the steps are still pretty much the same:
https://firebase.blog/posts/2016/12/working-with-multiple-firebase-projects-in-an-android-app.
You can find the OAuth2 client ID on the
Google Cloud console API Credentials page for your Play project under OAuth2 Client IDs. Locate the client name--it'll be named something like "Android client for
your.bundle.name (auto created by Google Service." Click the Download icon on the far right and it'll pop up the client ID (it'll end in `
apps.googleusercontent.com`). Copy that ID and paste it into the Firebase console via
Authentication > Sign-in Providers > Google > Edit > Safelist Client IDs from External Clients and click Save. You'll also want to re-download your google-services.json file and add it to your app and hopefully that will do the trick!
You can find the full instructions for this @
I need to retain the OAuth client in a different project but want to share Google Sign-in (or the blog post--the UI has changed a bit, but the steps are the same!).