Members - Missing Approver field on confirm page when second approver is added offline

[mitarachim]

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.3.15-1
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #79878
Email or phone of affected tester (no customers): sodinjsodsjdoijsoni@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Workspace is on Control plan.
• User has invited member B to the workspace.

1. Go to staging.new.expensify.com
2. Go to workspace settings > Workflows.
3. Go offline.
4. Edit the existing workflow and make member B be the second approver.
5. Go to workspace settings > Members.
6. Enter user C email and select the user > Next.
7. Go online.

Expected Result:

In Step 6, Approver field will appear on the confirm page when the second approver is added offline.

Actual Result:

In Step 6, Approver field does not appear on the confirm page when the second approver is added offline.
In Step 7, Approver field only appears on confirm page after returning online.

In the reverse scenario where the second approver is removed offline, Approver field still shows up on invite member confirm page when it should disappear.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari

Screenshots/Videos

Bug7069083_1770355004732.9.mp4

View all open jobs on GitHub

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #79878

[melvin-bot]

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

[melvin-bot]

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

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