Domains - Not here RHP on Requestor side after Admin deny request

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

---

Version Number: v9.4.77-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #100161
Email or phone of affected tester (no customers): leungbratt6@gmail.com/ admin@expplause.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Windows 10/Chrome
App Component: Workspace Settings

Action Performed:

1. Sign in as User A, who is an admin of a domain (e.g. domain.com).
2. Sign in as User B in another browser/incognito window.
3. As User B, go to Workspaces > Domains > New, and try to add domain.com.
4. On the "Domain already exists" screen, tap Request access - Click on the new request Domain
5. As User A, go to Workspaces > Domains > domain.com > Domain Admins
6. Tap Deny
7. Switch to the User B tab

Expected Result:

No not here page , the RHP dismisses smoothly

Actual Result:

Not here RHP appears after Admin denies the request

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7257742_1789199261950.not_here_domain.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7257742

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/402fd72dd97ea1da8a04b9a189471368980597cab21a8bce5f74b11801628d4a

[melvin-bot]

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

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

[melvin-bot]

@mountiny @ZhenjaHorbach you have been assigned to this deploy blocker because you reviewed the offending PR: #100161

[melvin-bot]

@jakubstec you have been assigned to this deploy blocker because you authored the offending PR: #100161

[melvin-bot]

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