Android - Reports - "Filter for expenses that need approval" tooltip is displayed cutted off

[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.1.42-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): ibellicotest+683@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 - Android 12
App Component: Other

Action Performed:

1. Open the Expensify app.
2. Sign up with a new account.
3. Create a new workspace.
4. Navigate to "Reports"
5. Note that the tooltip displayed on outstanding filter is displayed cutted off.

Expected Result:

"Filter for expenses that need approval" tooltip should be completelly visible.

Actual Result:

"Filter for expenses that need approval" on outstanding tab on "Reports" is displayed cutted off and the "X" button to dismiss it can´t be reached. User has to scroll the filters to see the tooltip complete.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6825034_1746665933795.Cutted.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @CortneyOfstad (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]

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

[marcaaron]

Appears to be introduced by #59950 cc @ishpaul777 @MarioExpensify

Honestly, does not look so bad to me - but maybe could be improved? I think we make this a non-blocker or perhaps even close.