something went wrong #332

GOLHS · 2024-01-13T19:41:09Z

error Error: Something went wrong
at returnResult (VM3:912:32)
at win.androidBridge.onmessage (VM3:887:21)

malvinder · 2024-01-16T07:13:02Z

Facing the same issue with error code 10
I have tried all the web client id, server client id, android client id and everything, replacing them with each other.
Still the same error.

agnusdei1207 · 2024-01-27T08:59:10Z

I also faced the same problem

agnusdei1207 · 2024-02-08T15:02:21Z

just now i clear it that issue!

https://velog.io/@agnusdei1207/angular-ionic-capacitor-google-oauth2-plugin-feat.-android-ios

sha-1 key issue..!
only use android studio tool gradle and use gradle signingReport

The sha-1 key continues to change depending on how it is generated.
The most stable method is the above method.

RobinRosculete · 2024-03-21T03:36:20Z

Facing the same issue. Not sure what it is as it was working before. Did anybody find a solution?

alon42 · 2024-03-26T16:14:44Z

Same problem here...
Couldn't find any solution yet.

@RobinRosculete

Naza2021 · 2024-03-28T16:58:17Z

I was struggling with this error for hours!!! But then, while checking the demo and following the readme.md, I realized that I was missing a configuration in a file: android/app/src/main/res/values/strings.xml

In the demo, you can find it at: https://github.com/CodetrixStudio/CapacitorGoogleAuth/blob/master/demo/android/app/src/main/res/values/strings.xml

Once I added the with the Google clientId, everything started to work :)

Good day <3

alon42 · 2024-03-29T15:55:04Z

Finally managed to make it work!!
Ionic - vue

under android/app/build.gradle make sure to change applicationId and have your UNIQUE application ID
run cd android > ./gradlew signInReport
Scroll all the way up(!!!!) and copy the sha1 key of the debug varient
open your browser with https://console.cloud.google.com/apis/credentials
create android(!) credentials,
VERY IMPORTANT:
use the same applicationId from android/app/build.gradle and use the SHA1.
save...

WE ARE NOT GOING TO USE THE ANDROID KEY BUT WITHOUT IT CapacitorGoogleAuth WILL NOT WORK.

in your app just use your web credentials (!!!)

Error 10 comes from Google API exception, and it signals that the android package name and sha1 are not valid

bobbyg603 · 2024-04-02T18:18:04Z

Thank you @alon42, this worked for me. To further clarify step 2 for the next person the SHA1 I needed was specifically the one under > Task :app:signingReport.

RobinRosculete · 2024-04-05T20:58:49Z

Thank you so much @alon42, It finally worked !

kristophbarbour · 2024-04-18T09:11:27Z

I have done all of the above and even followed @agnusdei1207 's awesome instructions and still I get Something went wrong Error 10.
Has anyone else found any other solutions?

alon42 · 2024-04-18T10:22:03Z

@kristophbarbour
Error 10 comes from the Google API itself.

I was desperate enough to find its source code when I searched for this problem 3 weeks ago, and it comes from having bad Android credentials. when there is something wrong with your ApplicationId with the SHA1.

make sure you are using:

a. google WEB credentials in the Capacitor config.
b. you created an android credentials WITHOUT using them.
b1. Under Android credentials, you use a unique Application Id (I failed there) from android/app/build.gradle.
b2. you are using the correct SHA from the output of cd android and then ./gradlew signInReport.
b3. you wait enough time to let the cache in Google servers clear itself (they day 5 minutes).

Raja-Malli-Dileep-Vadde · 2024-05-07T10:27:33Z

Actually, i am also totally confused about google signing in ionic app but, i got to know solution by several tries, i finally discovered that the debug keystore SHA1 only works in the emulator

Here,

1.debug keystore SHA1 works only in emulator (to get debug keystore SHA1 in terminal enter this commands cd android and then ./gradlew signInReport)

release keystore SHA1 works only in app.release.apk (to get release keystore SHA1 in terminal enter this commands keytool -keystore ./my-release-key.keystore -list -v )
(In commands this “./my-release-key.keystore” is path of production keystore path)
In live playstore SHA1 works only in live app (Downloaded For playstore) (to get live playstore SHA1 Go to Play store Console and setup >> App signing (inside App signing you have App signing key certificate >>SHA-1 certificate fingerprint )

we should change SHA1 of Android SHA-1 signing certificate fingerprint. accordingly, in https://console.cloud.google.com (APIs & Services>>Credentials>>OAuth 2.0 Client IDs)

Please make sure clear app data and try 2 times while checking login functionality

Raja-Malli-Dileep-Vadde · 2024-05-07T12:14:08Z

I have done all of the above and even followed @agnusdei1207 's awesome instructions and still I get Something went wrong Error 10. Has anyone else found any other solutions?

Please check #332 (comment)

Raja-Malli-Dileep-Vadde · 2024-05-07T12:14:56Z

Facing the same issue with error code 10 I have tried all the web client id, server client id, android client id and everything, replacing them with each other. Still the same error.

#332 (comment)

Raja-Malli-Dileep-Vadde · 2024-05-07T12:15:26Z

error Error: Something went wrong at returnResult (VM3:912:32) at win.androidBridge.onmessage (VM3:887:21)

#332 (comment)

Raja-Malli-Dileep-Vadde · 2024-05-07T12:15:36Z

Facing the same issue with error code 10 I have tried all the web client id, server client id, android client id and everything, replacing them with each other. Still the same error.

#332 (comment)

arielhasidim · 2024-06-03T17:51:05Z

I managed to use the GoogleAuth plugin on Android, but it only worked with the debug version (simulator or actual device), but the same build failed on the release version.

Using @Raja-Malli-Dileep-Vadde #332 (comment), I FINALLY SUCCEEDED BY MANUALLY ADDING THE SHA-1 FROM GOOGLES PLAY-STORE AND ADD IT ONTO A NEW CREDENTIAL IN GCS (all without pushing a new version!).

Steps:

Copy the "SHA-1 certificate fingerprint" from Google Play Console >> Setup >> App signing
Manually add a new Android credential in the GCS Credential API with the SHA-1 fingerprint you just copied (I copied all the other fields from the old ones that I left untouched)
Enjoy

By the way, does this belong to the official instructions? @reslear @fullstackduck

Maybe it also relates #220, #110

lsantaniello · 2024-06-20T09:07:02Z

I have the same issue but I can't solve. My problem is for Android device only. iOS is ok

What about angular config and files:

Angular init:
GoogleAuth.initialize({});

capacitor.config.ts

plugins: {
    CapacitorHttp: {
      enabled: true,
    },
    GoogleAuth: {
      scopes: ['profile', 'email'],
      iosClientId: "359711685XXX-653hlg3028afl02tbchp96XXXXXXX.apps.googleusercontent.com",
      androidClientId: "359711685XXXX-1eeonchhkt6k074ji3XXXXXXXX.apps.googleusercontent.com",
      forceCodeForRefreshToken: true,
    },
  }

google-services.json file into my ionic app into .\android\app\google-services.json

Please help me

lsantaniello · 2024-06-20T10:22:30Z

There are 2 SHA-1 code. What is the correct to copy?

arielhasidim · 2024-06-20T15:34:10Z

@lsantaniello

Use the "App signing key certificate" and add it like the screenshot above
In the capacitor.config.ts, you have a real ClientId without XXs, right?

lsantaniello · 2024-06-20T15:42:40Z

Yes, correct. I tried but not works :(

Are you available for premium support? If you can and you want help me, send me your private contact, please

arielhasidim · 2024-06-20T15:52:25Z

@lsantaniello Sorry, I'm just a struggling developer like you :|

lsantaniello · 2024-06-20T17:01:51Z

@lsantaniello Sorry, I'm just a struggling developer like you :|

if you want we can schedule a working session in order to solve the issue all together

denesh-r · 2024-07-03T12:14:46Z

I was struggling with this error for hours!!! But then, while checking the demo and following the readme.md, I realized that I was missing a configuration in a file: android/app/src/main/res/values/strings.xml

In the demo, you can find it at: https://github.com/CodetrixStudio/CapacitorGoogleAuth/blob/master/demo/android/app/src/main/res/values/strings.xml

Once I added the with the Google clientId, everything started to work :)

Good day <3

I was developing a second version of my ionic/capacitor app. I wanted to start fresh, so created a new project and copied over all the necessary configs.
However I was getting this code 10 error.

Finally the config mentioned above sorted it out.
Weird, how the old project still worked.

Maybe because I switched the GoogleAuth plugin to a newer one.

I ran into code 10 when I was working on the first version, and went through all the SHA1 setup and all.
And I ran into it the second time, but this time was totally different 🤷‍♂️

lsantaniello · 2024-07-13T11:33:22Z

I not solved!

almiavicas · 2024-09-16T04:41:54Z

I finally got it to work, @Raja-Malli-Dileep-Vadde was right.

On development (emulator devices), the SHA-1 you should use is the one that is generated by ./gradlew signInReport.
Live, when publishing the app on the Play Store, you have to use the SHA-1 that Play Store gives you.

In the end, for my case I'll keep two different Android OAuth client IDs. One for dev (emulators) and one for prod (play store).

This is really annoying, I spent a few days solving this, but thank you to the amazing community that shares knowledge and helps everyone grow. You rock!

almiavicas · 2024-09-25T15:33:25Z

I finally got it to work, @Raja-Malli-Dileep-Vadde was right.

On development (emulator devices), the SHA-1 you should use is the one that is generated by ./gradlew signInReport.

Live, when publishing the app on the Play Store, you have to use the SHA-1 that Play Store gives you.

In the end, for my case I'll keep two different Android OAuth client IDs. One for dev (emulators) and one for prod (play store).

This is really annoying, I spent a few days solving this, but thank you to the amazing community that shares knowledge and helps everyone grow. You rock!

Update, for everyone else figuring this out:

In my latest version I realized that I do not need at all the android Oauth client id. Only configuring the server client id is enought (basically the web oAuth client id).

Place that client id on the values.xml file and on your capacitor config, and then build the app.

This is only for android devices

juanbrein · 2024-12-09T17:40:35Z

Not sure if this has been said but... if you plan to release your app with google authentication in the play store, you have to get the SHA1 that is in the final APK. That is you have to download the APK from the google play store and run keytool -printcert -jarfile file.apk to get the SHA1, configure it in the Google Cloud Console and it will work

riderx · 2024-12-10T18:25:22Z

Do not forget to migrate to the new lib who implements Google auth latest lib, is well documented around this:
https://github.com/Cap-go/capacitor-social-login
The current repo is not maintained and lib used will be deprecated by Google in January.
We tried to contact the owner of the repo unsuccessfully, so we added to the README the new plugin recommendation.

riderx · 2025-01-13T18:11:00Z

We updated the README to make it extra clear, please migrate to https://github.com/Cap-go/capacitor-social-login/tree/main

This was referenced May 7, 2024

Getting error Something went wrong, code: 10 #291

Open

Always showing 10:Something Went Wrong error - Ionic5 Capacitor4 Android #220

Open

arielhasidim mentioned this issue Jun 14, 2024

Something went wrong, error code 10 on Android #371

Open

theophane-girard mentioned this issue Sep 25, 2024

Getting error Something went wrong, code: 10 - ISSUE HAPPENING AGAIN - SHA1 KEY ADDED ALREADY - STILL ISSUE PERSISTS - #291 RE-HAPPENING #380

Open

skidrow88 mentioned this issue Jan 9, 2025

Getting error after GoogleAuth.signIn() #400

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

something went wrong #332

something went wrong #332

GOLHS commented Jan 13, 2024

malvinder commented Jan 16, 2024

agnusdei1207 commented Jan 27, 2024

agnusdei1207 commented Feb 8, 2024

RobinRosculete commented Mar 21, 2024 •

edited

Loading

alon42 commented Mar 26, 2024

Naza2021 commented Mar 28, 2024

alon42 commented Mar 29, 2024

bobbyg603 commented Apr 2, 2024

RobinRosculete commented Apr 5, 2024

kristophbarbour commented Apr 18, 2024

alon42 commented Apr 18, 2024 •

edited

Loading

Raja-Malli-Dileep-Vadde commented May 7, 2024 •

edited

Loading

Raja-Malli-Dileep-Vadde commented May 7, 2024

Raja-Malli-Dileep-Vadde commented May 7, 2024

Raja-Malli-Dileep-Vadde commented May 7, 2024

Raja-Malli-Dileep-Vadde commented May 7, 2024

arielhasidim commented Jun 3, 2024

lsantaniello commented Jun 20, 2024 •

edited

Loading

lsantaniello commented Jun 20, 2024

arielhasidim commented Jun 20, 2024

lsantaniello commented Jun 20, 2024 •

edited

Loading

arielhasidim commented Jun 20, 2024

lsantaniello commented Jun 20, 2024

denesh-r commented Jul 3, 2024

lsantaniello commented Jul 13, 2024

almiavicas commented Sep 16, 2024 •

edited

Loading

almiavicas commented Sep 25, 2024 •

edited

Loading

juanbrein commented Dec 9, 2024

riderx commented Dec 10, 2024

riderx commented Jan 13, 2025 •

edited

Loading

something went wrong #332

something went wrong #332

Comments

GOLHS commented Jan 13, 2024

malvinder commented Jan 16, 2024

agnusdei1207 commented Jan 27, 2024

agnusdei1207 commented Feb 8, 2024

RobinRosculete commented Mar 21, 2024 • edited Loading

alon42 commented Mar 26, 2024

Naza2021 commented Mar 28, 2024

alon42 commented Mar 29, 2024

bobbyg603 commented Apr 2, 2024

RobinRosculete commented Apr 5, 2024

kristophbarbour commented Apr 18, 2024

alon42 commented Apr 18, 2024 • edited Loading

Raja-Malli-Dileep-Vadde commented May 7, 2024 • edited Loading

Raja-Malli-Dileep-Vadde commented May 7, 2024

Raja-Malli-Dileep-Vadde commented May 7, 2024

Raja-Malli-Dileep-Vadde commented May 7, 2024

Raja-Malli-Dileep-Vadde commented May 7, 2024

arielhasidim commented Jun 3, 2024

lsantaniello commented Jun 20, 2024 • edited Loading

lsantaniello commented Jun 20, 2024

arielhasidim commented Jun 20, 2024

lsantaniello commented Jun 20, 2024 • edited Loading

arielhasidim commented Jun 20, 2024

lsantaniello commented Jun 20, 2024

denesh-r commented Jul 3, 2024

lsantaniello commented Jul 13, 2024

almiavicas commented Sep 16, 2024 • edited Loading

almiavicas commented Sep 25, 2024 • edited Loading

juanbrein commented Dec 9, 2024

riderx commented Dec 10, 2024

riderx commented Jan 13, 2025 • edited Loading

RobinRosculete commented Mar 21, 2024 •

edited

Loading

alon42 commented Apr 18, 2024 •

edited

Loading

Raja-Malli-Dileep-Vadde commented May 7, 2024 •

edited

Loading

lsantaniello commented Jun 20, 2024 •

edited

Loading

lsantaniello commented Jun 20, 2024 •

edited

Loading

almiavicas commented Sep 16, 2024 •

edited

Loading

almiavicas commented Sep 25, 2024 •

edited

Loading

riderx commented Jan 13, 2025 •

edited

Loading