Google SSO not working on Android builds signed by Google

[Julesssss]

Problem

On staging build 9.1.74-4 Google SSO doesn't seem to work as we remain on the Auth. It works on iOS. I imagine this will be raised by QA but in the meantime I am investigating.

• 9.1.74-4 production build ❌ (signed with google's key!!)
• 9.1.74-4 AdHoc build ✅
• 9.1.74-4 local signed build ✅

Solution

Generate a debuggable locally signed build and triage with local and server logs.

Update the Google web clientID to use one hidden in an older google cloud project

[melvin-bot]

Triggered auto assignment to @mollfpr (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[Julesssss]

I think it's likely the Google Cloud registered clientIDs. Next step is to use an Android Studio tool and Play Store console to make sure we've registered the correct keys.

Plan:

• Check for logs on backend
• Check AdHoc build branched from staging
  • If it works then it's probably app signed key
  • If it doesn't work then it's likely code
• Check local signed build
  • If it works then it's the google signed APK
  • If it doesn't work then bug in Google Library?

[Julesssss]

I have the SHAs, but they are all already registered with Google Auth.

One thing I noticed is that the signing key is flagged with `Another project contains an OAuth 2.0 client that uses this same SHA-1 fingerprint and package name combination Learn more (guidence)