DOCS ISSUE: Error code 10 in Capacitor 4 with Google Auth in Android

[j-d-carmichael]

We are using Capacitor v4.7.0

We use Firebase for push notifications (https://capacitorjs.com/docs/guides/push-notifications-firebase)

We use Google and Facebook for SSO on the web and have had no issues before and after starting to integrate Google SSO in the app.

In fact, the Facebook (https://github.com/capacitor-community/facebook-login) login is integrated into our Android app just fine.

We're getting dizzy running through all the rabbit warrens of guides....

Issue/Question 1: For Google SSO to work with this plugin, do we need to use Firebase?

A lot of the SO posts and other guides point to using Firebase for SSO - but this makes no sense to us as we have our own server for authentication, and it works fine for Google SSO via our web app. We just passed a token to google from the client and all is good.

Issue/Question 2: Do we have to wait for the new Android OAuth to be approved?

When we added the Android OAuth key, we noticed that the google OAuth consent screen changed; we now have " Verification in progress" again. So, we're hoping it is just this, but Google is not helpful in any way there to know what is what.

---

We spent a good number of hours trying to get this to work, but we only seem to be able to get in return error #10 without any further info from Google.

We have done the following to try and get this to work:

1. Added the SHA1 to our firebase Push Notification project.
2. Added the android OAuth key and the server id to the capacitor.ts file as illustrated here: https://github.com/CodetrixStudio/CapacitorGoogleAuth/#configure
3. Added all the android code and js code
4. But... nothing works - we only get error 10.

[j-d-carmichael]

We solved this crazy issue!

The key was getting the client ID from the google-services.json file, which is actually the client ID for firebase and nothing mentioned in any Google OAuth!!!

On Firebase itself, head to build -> authentication, then on the signing method tab you have to add Google as an additional provider.

Then magically is just worked!

There was no mentioned on this in these docs, or Google docs... just a series of trial and error and digging through other issues. Completely mad.

[j-d-carmichael]

The issue here is that this should be documented in this plugin... almost any app today uses push notifications.

Push notifications with CapacitorJS will invariably lead to using firebase.

And unless we missed something, this use of Firebase for Push notifications means you have to use Firebase for GoogleSSO.

And if you have to use Firebase either way... it would help a lot of people by adding this to this projects readme :)

[nihalojha]

Hey,

I am also facing this exact same issue and I have been searching for a solution for a long time now. I have used the web client ID mentioned in google-services.json and also have enabled the google provider in Firebase. It works in development mode, but as I publish my app on play store, it gives error code 10. Please let me know, if you find any solution for this.

[j-d-carmichael]

Yes, we got a little ahead of ourselves.
It worked in development mode only.

We noticed the addition of the Android OAuth key to google resulted in the AuthScreen status moving to in verification... we can only assume that when this resolves, everything will start working again.

[nihalojha]

Thanks for the prompt reply. Please notify me, if you find any work around for this. 🙏

[j-d-carmichael]

And vice versa... or any advice from @fullstackduck :)

[fullstackduck]

@j-d-carmichael It's been like 3 years since I moved away from Capacitor, @reslear has been maintaining this plugin 😅
PRs and maintainers are welcome. Hope you figure this out.

[j-d-carmichael]

@fullstackduck you are the top contributor and the only face I could see on the parent page :D

I can see a published fork by you @reslear but I guess then you took over this one now?

[reslear]

@j-d-carmichael fork only for testing - actual code data in this repo.
Add more info, add reproduction maybe community can help you.
Also PR welcome.

--

[sourcer18]

The same thing happens to me, I need help. A few weeks ago it was working fine.

[j-d-carmichael]

@reslear i love that response with gpt hahahaha ❤️❤️ but yea we tried all of that and some... our only conclusion is to wait until the new oauth consent screen is verified... the message they offer is:

Verification status
Verification in progress
The Trust and Safety team has received your form. They will contact you by email if necessary. The review process can take up to 4–6 weeks. Expect the first email from our Trust and Safety team within 3–5 days. Your last approved consent screen is still in use. Learn more

Also this PR from @axi sounds like it needs resolving before the end of the month so maybe this is just all a series of bad timing. It just looks like he is awaiting some feedback from @sjdrew : #259

But for sure, if we later see things to improve, I'll see what we can do on the PR front.

[sourcer18]

Good morning, I have solved it. After discarding everything I came to the conclusion that the sha-1 was not correct. I added the sha-1 that I had in the app on the firebase and that solved it.

[j-d-carmichael]

Amazing! @sourcer18 does this also now work in production mode?

[sourcer18]

@j-d-carmichael Yes, I have generated the application in release mode in android studio after having generated the capacitor and it works correctly.