BigBalli commented on issue #429:
URL: https://github.com/apache/cordova-cli/issues/429#issuecomment-4179809440
Hey — this looks like a Firebase/Google Cloud Console configuration issue
rather than a Cordova bug. The `"Requests from this Android client application
<empty> are blocked"` error means Google isn't receiving your app's package
name or SHA-1 signing certificate, so it can't match the request to an
authorized client.
A few things to check:
1. **SHA-1 fingerprint**: Make sure you've added your debug (and release)
signing key's SHA-1 fingerprint in the Firebase Console under Project Settings
> Your Android App. You can get it with:
```
keytool -list -v -keystore ~/.android/debug.keystore -alias
androiddebugkey -storepass android
```
2. **Package name**: Verify the package name in Firebase Console matches
your Cordova app's `id` in `config.xml` (in your case `com.domain.app` or
whatever your actual app ID is).
3. **OAuth redirect**: Since you're using Facebook OAuth through Firebase,
make sure the OAuth consent screen and authorized redirect URIs are configured
for your Android app, not just the web client.
4. **Version note**: cordova-android 7.1.4 is very old at this point — if
you're still working on this project, upgrading to a recent version might also
help since the WebView and intent handling have improved significantly.
This is likely not a Cordova CLI issue — you'd hit the same problem with any
Android build tool if the Firebase config is incomplete.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
