Replies: 1 comment
-
|
Firebase google-services.json contains multiple client IDs — but for AAB builds, Firebase alone isn’t enough. You must register and configure the correct OAuth Client ID in Google Cloud Console, tied to your Play App Signing SHA-1. Solution: If you're using @react-native-google-signin/google-signin with Firebase Auth in a React Native app and it's only failing on AAB builds (production), here's what worked for me: Key Fix: For Production (AAB Build): You must use the OAuth 2.0 Web Client ID created in Google Cloud Console, not the Android client ID. If you don’t already have a matching Web Client ID: Go to Google Cloud Console Create a new OAuth 2.0 Client ID (Web Application) Use the same package name Then update your app config: |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
for anyone encounters this issue in production for internal test, consider migrating to Firebase and adding the Google SHA-1 keys to it. I struggled with this error for a day, but after switching to Firebase, it worked perfectly. For the webclientid, use the client_id from the client_type: 3 in the google-services.json file provided by Firebase.
Beta Was this translation helpful? Give feedback.
All reactions