[HOLD for payment 2024-07-24] Desktop - Unable to login Google/ Apple button

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 9.0.6-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4708479
Email or phone of affected tester (no customers): rybkina@gmail.com
Issue reported by: Applause - Internal Team

Action Performed:

1. Launch App
2. Tap on Google/ Apple button on sign in page
3. Tap on Allow on popup on web " Do you want to allow this website to open “New Expensify”?

Expected Result:

Desktop App should be open as login user via Google/ Apple

Actual Result:

Desktop App opens on sign in page but not login

Workaround:

Unknown

Platforms:

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

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6538976_1720705331685.google.mp4

View all open jobs on GitHub

[melvin-bot]

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

[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]

Quite possibly related to our other redirect blockers. Discussing in Slack.

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[luacmartins]

Fixed here

[kavimuru]

Issue is not fixed.

20240712_203845.1.mp4

[Julesssss]

Issue is not fixed.

Hey @kavimuru, we think this was fixed. Is the desktop version up to date?

[kavimuru]

@Julesssss Build is not updated to the latest.

[luacmartins]

@kavimuru Can we test on the latest build please?

[kavimuru]

Bug is fixed

fixed.2.mp4

[Julesssss]

Closing as no longer reproducible ❤️

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.7-8 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [CP Staging] Revert "Fix show onboarding modal functions" #45299

If no regressions arise, payment will be issued on 2024-07-24. 🎊