[$250 reproduction steps][CRITICAL] Login - Unable to sign in with Google

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Deliverable

The deliverable is to provide reliable reproduction steps for the bug. - Follow the Propose a solution for a job process to submit the steps for review”. Inc. preconditions and additional details if they’re helpful. (ie. require x beta to be enabled, must be on a Collect plan)

Version Number: 9.0.89-2
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: #55521
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause - Internal Team

Action Performed:

1. Open the Hybrid Android app
2. Tap on Continue with Google
3. Choose an account

Expected Result:

The app leads to the Inbox screen

Actual Result:

An error message is displayed

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6720072_1737480252044.Sign-in_with_Google.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021889704177684673850
• Upwork Job ID: 1889704177684673850
• Last Price Increase: 2025-02-12
• Automatic offers:
• DylanDylann | Reviewer | 106658000

Issue Owner

Current Issue Owner: @DylanDylann

[melvin-bot]

Triggered auto assignment to @strepanier03 (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[mountiny]

Adding backend Deploy blocker as it was also repro in production but its a serious bug

[melvin-bot]

Triggered auto assignment to @tgolen (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.

[mountiny]

Asked QA about the reproducability https://expensify.slack.com/archives/C9YU7BX5M/p1737756072117619

Since its repro in production, it is technically not a blocker, might be some auth change or web change, but if this is happening commonly it should be treated with urgency, hence I applied the labels

[mountiny]

Found logs for the user listed but there is no error

[tgolen]

That's pretty strange that it would only happen on Android, if it was a backend problem. I would think that would fail on all platforms if it was a backend problem.

[mountiny]

Qa confirmed in slack they cannot reproduce anymore - i have asked them still for more details if we could figure out what caused this outage.

[tgolen]

OK, since it cannot be reproduced, I will close this.

[mitarachim]

QA team can repro this issue in Hybrid Android - STG build 9.0.97-0

XRecorder_20250212_02.mp4

[tgolen]

I'll see if we can get some external help to triage this.

[melvin-bot]

@DylanDylann Eep! 4 days overdue now. Issues have feelings too...

[tgolen]

This one sure comes and goes. I think it would be great if we assign this to one of our expert agencies and really have them do a deep dive an investigation into the bug.

[mitarachim]

QA team could repro this issue again in Hybrid Android - STG build 9.1.15-0

az_recorder_20250318_213700.mp4

[melvin-bot]

@DylanDylann 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

[tgolen]

Daily Update

• I posted in Slack to see if one of our expert agencies could look into this

Next Steps

• See if an expert agency is able to pick this up and discover the problem

ETA

• Friday, Mar. 28 to have some kind of plan for this

[sosek108]

Hi, I'm Hubert from Callstack - expert contributor group. I'd like to look into this issue.

Unfortunately I was not able to reproduce this, so could you provide some logs as mentioned here?

[melvin-bot]

📣 @DylanDylann 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app!

Offer link
Upwork job

[mallenexpensify]

Posted in #qa for a retest.

Can I get a retest on this issue? We're having reproducing so, can the tester include profiling and client side logs with their retest? Thx

[m-natarajan]

Able to reproduce , Unable to collect profiling and client side logs as user was not able to signin

Retest.55682.mp4

[mallenexpensify]

Unsure of next steps cuz QA is able to reproduce yet @sosek108 and I aren't
@DylanDylann are you able to repro?

Posted in the Slack thread and shared with room to see if this is widespread.

[sosek108]

@m-natarajan did you test on Staging or Prod?

[sosek108]

With help of @mountiny I've checked logs of adhoc build and it says Expensify: [warn] (anonymous) Google signIn callback returned error: DEVELOPER_ERROR. This error most probably means build misconfiguration. To properly use Google SSO there is a need to add application signing key to Firebase.

I've double checked that with build 9.1.15-9 which is current production build. When I tried login with production application (downloaded from Google Play) it worked fine, but when I installed this build from here https://github.com/Expensify/App/releases it results in error.

I suggest that person who has access to Expensify's Firebase and application builds double check if signing key of staging and adhoc builds are properly set in Firebase.

@m-natarajan to confirm that theory I need information that if you could reproduce this on production version?

[mountiny]

@sosek108 I check the firebase setup but it seems like its all correct :/

[sosek108]

I've noticed that PROD has been updated to 9.1.18-4. Google SignIn works on this prod version

[mountiny]

@tgolen do you know if this was reported by any customers? Maybe its related to the version switching that @sosek108 also noticed so then internal people and testers are prone to this issue but if customer just uses production it seems to work just fine

[tgolen]

I don't think it was reported by any customers, no. I'd be fine closing this as long as it cannot be reproduced on production. Is that the case?

…

On Tue, Apr 1, 2025 at 7:13 AM Vit Horacek ***@***.***> wrote: @tgolen <https://github.com/tgolen> do you know if this was reported by any customers? Maybe its related to the version switching that @sosek108 <https://github.com/sosek108> also noticed so then internal people and testers are prone to this issue but if customer just uses production it seems to work just fine — Reply to this email directly, view it on GitHub <#55682 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJMAB6GC4WYG7ALOHN44732XKGGPAVCNFSM6AAAAABVYNO6JOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONRZGMYTSMZXGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***> [image: mountiny]*mountiny* left a comment (Expensify/App#55682) <#55682 (comment)> @tgolen <https://github.com/tgolen> do you know if this was reported by any customers? Maybe its related to the version switching that @sosek108 <https://github.com/sosek108> also noticed so then internal people and testers are prone to this issue but if customer just uses production it seems to work just fine — Reply to this email directly, view it on GitHub <#55682 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJMAB6GC4WYG7ALOHN44732XKGGPAVCNFSM6AAAAABVYNO6JOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONRZGMYTSMZXGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[sosek108]

@mountiny @tgolen since I started working on that issue I had 0 reproduction rate on production. Although this is 100% reproducible on Adhoc, Staging and Dev builds.

I did more research on that and due to documentations and how-to's DEVELOPER_ERROR which is returned on Adhoc and Dev mode is connected to Firebase / Google Console configuration only.

[tgolen]

It would be nice if we could get it working on staging. Do you know why the DEVELOPER_ERROR doesn't happen on staging, but you can still reproduce the issue there? It's not the end of the world if it doesn't work on Staging, but not ideal.

…

On Tue, Apr 1, 2025 at 10:09 AM Hubert ***@***.***> wrote: @mountiny <https://github.com/mountiny> @tgolen <https://github.com/tgolen> since I started working on that issue I had 0 reproduction rate on production. Although this is 100% reproducible on Adhoc, Staging and Dev builds. I did more research on that and due to documentations and how-to's DEVELOPER_ERROR which is returned on Adhoc and Dev mode is connected to Firebase / Google Console configuration only. — Reply to this email directly, view it on GitHub <#55682 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJMAB57DHK5PYM6DIFGGWD2XK235AVCNFSM6AAAAABVYNO6JOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONRZHA4DEMRZGE> . You are receiving this because you were mentioned.Message ID: ***@***.***> [image: sosek108]*sosek108* left a comment (Expensify/App#55682) <#55682 (comment)> @mountiny <https://github.com/mountiny> @tgolen <https://github.com/tgolen> since I started working on that issue I had 0 reproduction rate on production. Although this is 100% reproducible on Adhoc, Staging and Dev builds. I did more research on that and due to documentations and how-to's DEVELOPER_ERROR which is returned on Adhoc and Dev mode is connected to Firebase / Google Console configuration only. — Reply to this email directly, view it on GitHub <#55682 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJMAB57DHK5PYM6DIFGGWD2XK235AVCNFSM6AAAAABVYNO6JOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONRZHA4DEMRZGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[sosek108]

@tgolen I assume this error also occurs on staging. But I cannot be sure as no debug logs are sent to logcat on staging / prod builds

[tgolen]

OK, thank you for clarifying.

…

On Tue, Apr 1, 2025 at 10:15 AM Hubert ***@***.***> wrote: @tgolen <https://github.com/tgolen> I *assume* this error also occurs on staging. But I cannot be sure as no debug logs are sent to logcat on staging / prod builds — Reply to this email directly, view it on GitHub <#55682 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJMABY6T5375YRJFY2YVZ32XK3T5AVCNFSM6AAAAABVYNO6JOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONRZHA4TOOBRG4> . You are receiving this because you were mentioned.Message ID: ***@***.***> [image: sosek108]*sosek108* left a comment (Expensify/App#55682) <#55682 (comment)> @tgolen <https://github.com/tgolen> I *assume* this error also occurs on staging. But I cannot be sure as no debug logs are sent to logcat on staging / prod builds — Reply to this email directly, view it on GitHub <#55682 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJMABY6T5375YRJFY2YVZ32XK3T5AVCNFSM6AAAAABVYNO6JOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONRZHA4TOOBRG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[tgolen]

I'm going to close this for now. It can be reopened if it is reproducible in production.