You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Search - Status bar scrolls back after selecting Paid status #47674
Version Number: v9.0.22-5 Reproducible in staging?: Y Reproducible in production?: N Email or phone of affected tester (no customers):applausetester+kh050806@applause.expensifail.com Issue reported by: Applause Internal Team
Action Performed:
Launch New Expensify app.
Go to Search.
Scroll the status bar to the right.
Tap Paid.
Expected Result:
The status bar will not scroll back as this will block the view that Paid is selected (especially on a small/narrow screen).
Actual Result:
The status bar scrolls back when Paid status is selected, causing the selected status only partially visible.
👋 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:
Identify the pull request that introduced this issue and revert it.
Activity
melvin-bot commentedon Aug 19, 2024
Triggered auto assignment to @sakluger (
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 commentedon Aug 19, 2024
Triggered auto assignment to @stitesExpensify (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.IuliiaHerets commentedon Aug 19, 2024
We think that this bug might be related to #wave-collect - Release 1
github-actions commentedon Aug 19, 2024
👋 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:
rayane-d commentedon Aug 19, 2024
This is known and will be addressed as a follow-up in #47640
chiragsalian commentedon Aug 20, 2024
Closing issue since it will be addressed as a follow up.