Open lsantaniello opened 2 months ago
Maybe this will help: https://github.com/CodetrixStudio/CapacitorGoogleAuth/issues/332#issuecomment-2145794691
I tried but It doesn't work for me.
I integrated Google Oauth Sign In in my Ionic Capacitor App but I have an issue for Android Device only:
When the user clicks on the Google login button from the app, a popup appears to select the gmail account. Immediately afterwards the system goes into error and in the log I find this error:
{ "save": false, "callbackId": "21517523", "pluginId": "GoogleAuth", "methodName": "signIn", "success": false, "error": { "message": "Something went wrong", "code": "10" } }
I've read several posts and tried different solutions but I can't resolve the problem. I followed the following steps
1) I deleted all fingerprints from Firebase Console for Android application
2) I have deleted all references from Google Cloud Console Oauth 2.0 Client IDs for the Android application
3) Generated SHA using windows shell command keytool -keystore my-jks-file-path -list -v
Certificate fingerprints: SHA1: 56:5D:38:F2:D0:XX:XX:XX:XX:XX:D7:FB:56:7A:A2:D4:B5:1B:D0:C5
4) Add SHA certificate fingerprint from Firebase Console (Android Apps)
5) Google creae automatically reference into Google Cloud Console Oauth 2.0 Client IDs (Android client for
6) Downloaded google-services.json file-path
7) Copied google-services.json file into my ionic app into .\android\app\google-services.json
8) Rebuild App using
9) Installed on my android device
I'll pay for support
Any update on this? I'm implementing this and just ran into this issue :(
I added my app SHA-256 in Firebase and it is started working for web application
in android folder I executed following command in command prompt gradlew signInReport
and copy SHA1 to Firebase SHA certificate fingerprints and same I did for SHA-256. While debugging it is not working but after deployment it is working fine without any issue
Just an update from me:
As mentioned in other threads, we should be using the web app key for Android. Additionally, the SHA-1 for each keystore and the Google Play Console all need to be included on the certs page in the Google Console.
Each type of build has a SHA-1 that needs to be available on the Google Console for sso to work on android. I recommend fetching the SHA-1 for the debug keystore, the generated keystore you use to sign your app, and the SHA-1 available on the Play Console. If set up correctly, the SSO should go through. If not, then the SHA-1 for the version you're running isn't available on the Google Console.
Hi Have you got any solution for this issue?
Yes! complete solution is around SHA-1 and SHA-256 But I guess this repository need more documentation. Version should be updated to redirection and callback function. Refer to my previous post https://github.com/CodetrixStudio/CapacitorGoogleAuth/issues/371#issuecomment-2225292476
I integrated plugin on my ionic capacitor app. On iOS, it works. On Android Device I always receve this error:
I configured all as wiki but I can't solve.
I have some doubts: 1) Downloaded from firebase console my google-services.json. Is it required? Where I need to save it?
2) I can't have "capacitor.config.json" file. I have only capacitor.config.ts
3) In google-service.json file there are several codes:
4) What is "serverClientId"?
5) What is the crrect SHA-1 to register at Android Console? a) That present in Google Play Console? b) Thant generate from command line (keytool -keystore MYKEYSTORE -list -v)?
My google-services.json file is:
My capacitor.config.ts
As "androidClientId" I used "client.oauth_client.client_id". The same of there is on Google Cloud Console, OAuth 2.0 Client IDs as "[Android client for it.gemarexpress (auto created by Google Service)]"