Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
aoneahsan opened this issue Jul 16, 2024 · 9 comments

Comments

@aoneahsan
Copy link

just for record

i have added the "SHA1" key of android studio "the debug key", the SHA1 key of released apk

i used these commands to get the SHA1 keys

to get the android studio debug SHA1 key
keytool -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android -keypass android

to get the bundled apk SHA1 key
keytool -printcert -jarfile app-release.apk

and yes i know about the play store signing key as well.

right now, i'm trying to make this package work on android emulator, and i'm getting this "code:10, message: 'something went wrong'" error

this is the package version i'm using
"@codetrix-studio/capacitor-google-auth": "^3.3.6",

and these are the capacitor packages versions
"@capacitor/android": "^6.1.0",
"@capacitor/app": "6.0.0",
"@capacitor/clipboard": "^6.0.0",
"@capacitor/core": "6.1.0",

@theophane-girard
Copy link

theophane-girard commented Aug 20, 2024

exactly the same issue here :/

@hobobemo
Copy link

I thought it was just me not being able to figure it out.

@almiavicas
Copy link

almiavicas commented Sep 11, 2024

Same issue here, I'll share my versions:

  • "@capacitor/android": "6.1.2",
  • "@capacitor/app": "6.0.1",
  • "@capacitor/core": "6.1.2",
  • "@codetrix-studio/capacitor-google-auth": "^3.4.0-rc.4",

If anyone solves this please share your solution. I'm working with an OAuth2 certificate generated on a Google Cloud Console project. I'm not using firebase.

To get the SHA-1 I did a different approach. I generated a key store with android studio, and I have a .jks file. Don't know if that changes something, but either way here is the command I used to get the SHA-1:

keytool -keystore <filename>.jks -list -v

I first tested with the SHA-1 fingerprint of the App signing key certificate generated by Google Play, but that didn't work. I suspect that it doesn't work because I am not using that certificate anywhere in my app so far. The only thing linking my app and the Google Play App should be the appId which I assume is not enough.

The OAuth client was first generated with the SHA-1 from Google Play. It did not work, I got the same error code 10. I then changed the SHA-1 to the one of my key store, but it is still failing

@veneliniliev
Copy link

did you find a solution?

@almiavicas
Copy link

I did find a solution, published in another ticket. I'm not in my computer right now so I can't provide you a link

@goemul39
Copy link

i had this, only solution i found was to use debug key because it's not possible to override it i think

@theophane-girard
Copy link

@almiavicas are you talking about this one ? issue 332

@almiavicas
Copy link

That's the one!

@theophane-girard
Copy link

worked for me by following this: #332 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants