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

Android only issue {"message":"Something went wrong","code":"12500"} #240

Open
choffmeyer opened this issue Nov 30, 2022 · 8 comments
Open

Comments

@choffmeyer
Copy link

having an issue with only android. ios and web works fine. based on the latest ionic/cap project i just created to see if this even works.

@choffmeyer choffmeyer changed the title {"message":"Something went wrong","code":"12500"} Android only issue {"message":"Something went wrong","code":"12500"} Nov 30, 2022
@choffmeyer
Copy link
Author

seems like this due to the emulator i'm using not having playstore installed as i'm seeing warnings when making the signin call to the plugin. If connect a real device it works.

@adrigardi90
Copy link

Confirmed. I got the same error via emulator with no Play Store installed. In a real device you don't have that issue.

@SourabhRavi
Copy link

I have a my apk installed on my phone, and it still shows this error

@AlvinTCH
Copy link
Contributor

AlvinTCH commented Apr 6, 2023

are you guys using Firebase? Do refer to the stackoverflow here. Might be resolved when the support email is added

https://stackoverflow.com/questions/47632035/google-sign-in-error-12500

@tarangshah19
Copy link

even without Firebase same issue comes i have use same sha1 from my android market also created released bundle also but same issue

@victorgoecking
Copy link

victorgoecking commented Jul 20, 2023

Same issue here, I even updated capacitor to v5 and google auth to 3.3.2 and nothing.
No local emulator works normally, but after being published on the store it gives this error.

@samuelrebuelta
Copy link

Same issue on cap v5 and 3.3.2 on published app but not always, some random times works... :(

@playaz87
Copy link

Adding a support email like @AlvinTCH suggested worked for me. We only use Firebase for FCM. All authentication is handled by our backend.

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

8 participants