mWeb - Tooltip - The FAB Tooltip doesn't reappear when a modal is closed.

[IuliiaHerets]

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.81-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: #54710
Email or phone of affected tester (no customers): biruknew45+4ppgp@gmail.com
Issue reported by: Applause Internal Team
Device used: mweb
App Component: Other

Action Performed:

1. Go to https://staging.new.expensify.com/
2. Log in as a new user.
3. To make the Concierge chat tooltip disappear, open the Concierge chat and then return back.
4. Now the FAB Tooltip appears.
5. Go to settings, then return to Inbox—the tooltip still appears.
6. Click on the workspace switcher, then navigate back.

Expected Result:

The FAB tooltip should reappear.

Actual Result:

The FAB tooltip disappears and doesn't reappear again.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6707629_1736200641878.1.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @ishpaul777

[melvin-bot]

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

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

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

[Beamanator]

noted PR that "caused" this in slack, i believe ishpaul is looking into this