Android应用修改包名后Firebase认证失败，Google Play上传遇阻求助

Hey there, let's work through this frustrating issue— I’ve dealt with exactly this scenario when rebranding apps for clients, so let’s break down the steps to get your auth working again:

1. Double-Check Firebase Console Configuration for Your New App #

• Confirm the package name/application ID in your Firebase console’s new app matches exactly what you’ve set in your project (case-sensitive, no typos!). Don’t just trust the name you entered— verify it against the applicationId in your build.gradle.
• Re-enable all authentication methods you were using before (e.g., Email/Password, Google Sign-In). New Firebase apps don’t carry over these settings from old apps by default.
• Add your app’s SHA-1 and SHA-256 fingerprints to the new Firebase app. This is the #1 most overlooked step— if you had fingerprints set for your old app, the new one needs the same debug/release fingerprints to work with auth providers like Google Sign-In.

2. Cleanly Replace & Sync google-services.json #

• Delete the old google-services.json from your app/ directory, then drop in the brand new one you downloaded from the Firebase console for your new app. Never manually edit this file— let Firebase generate it for you.
• Run a full Gradle sync: Click the "Sync Project with Gradle Files" button in Android Studio, or run ./gradlew clean build in your terminal to clear cached build artifacts. Old configs often stick around in cached files.

3. Verify Build.Gradle Application ID Settings #

• Open your app-level build.gradle file and check the defaultConfig block’s applicationId— it must match the package name you registered in Firebase.
• If you use product flavors, make sure each flavor’s applicationId (if overridden) also matches the corresponding Firebase app’s package name (if you created separate Firebase apps for flavors).

4. Hunt for Hardcoded Old Package Names in Code #

• Do a global search in your project for your old package name— it might be hiding in:
  • Custom auth logic or deep link URIs
  • GoogleSignInOptions configurations (check if you’re using a hardcoded client ID from the old app)
  • Firebase Dynamic Link or App Check settings
• Replace any instances with your new package name.

5. Wipe Old App Data & Reinstall #

• Uninstall the old version of your app from your device/emulator completely.
• Clear the emulator’s cache (if using one) or reset app storage on physical devices. Old shared preferences or cached auth tokens can cause conflicts with the new package name.
• Rebuild and reinstall the app from scratch.

6. Debug with Logcat #

If you’re still stuck, pull up Logcat in Android Studio and filter for keywords like FirebaseAuth, GoogleSignIn, or INVALID_CLIENT. The error messages here will tell you exactly what’s wrong— common issues include missing fingerprints, mismatched client IDs, or incorrect package name registrations.

Pro Tip #

If you’re using Firebase App Check, don’t forget to update the App Check configuration for your new app in the Firebase console— this is another easy-to-miss setting that can block auth flows.

内容的提问来源于stack exchange，提问作者Razvan