something went wrong

Question

something went wrong

GOLHS opened this issue 10 months ago · 27 comments

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

Answer 1 · 2024-01-16T07:13:02.000Z

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.

Answer 2 · 2024-01-27T08:59:10.000Z

I also faced the same problem

Answer 3 · 2024-02-08T15:02:21.000Z

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.

Answer 4 · 2024-03-21T03:36:20.000Z

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

Answer 5 · 2024-03-26T16:14:44.000Z

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

@RobinRosculete

Answer 6 · 2024-03-28T16:58:17.000Z

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

Answer 7 · 2024-03-29T15:55:04.000Z

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

Answer 8 · 2024-04-02T18:18:04.000Z

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.

Answer 9 · 2024-04-05T20:58:49.000Z

Thank you so much @alon42, It finally worked !

Answer 10 · 2024-04-18T09:11:27.000Z

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?

Answer 11 · 2024-04-18T10:22:03.000Z

@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).

Answer 12 · 2024-05-07T10:27:33.000Z

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

Answer 13 · 2024-05-07T12:14:08.000Z

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)

Answer 14 · 2024-05-07T12:14:56.000Z

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)

Answer 15 · 2024-05-07T12:15:26.000Z

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

#332 (comment)

Answer 16 · 2024-05-07T12:15:36.000Z

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)

Answer 17 · 2024-06-03T17:51:05.000Z

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

Answer 18 · 2024-06-20T09:07:02.000Z

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

Answer 19 · 2024-06-20T10:22:30.000Z

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

Answer 20 · 2024-06-20T15:34:10.000Z

@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?

Answer 21 · 2024-06-20T15:42:40.000Z

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

Answer 22 · 2024-06-20T15:52:25.000Z

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

Answer 23 · 2024-06-20T17:01:51.000Z

@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

Answer 24 · 2024-07-03T12:14:46.000Z

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 🤷‍♂️

Answer 25 · 2024-07-13T11:33:22.000Z

I not solved!

Answer 26 · 2024-09-16T04:41:54.000Z

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!

Answer 27 · 2024-09-25T15:33:25.000Z

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