[Due for payment 2025-04-03] Report- Report view shakes after returning from Reports & bottom tab moves after saving search

[mitarachim]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.1.9-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: Chat Report View

Action Performed:

Bug 1:

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Submit an expense.
4. Go to Reports.
5. Go to Inbox.
6. If the display is wide, page zoom in might be required to reproduce this issue.

Bug 2:

1. Go to staging.new.expensify.com
2. Go to Reports.
3. Click Filters.
4. Apply filter that will return results.
5. Click Save search.

Expected Result:

Bug 1: Report view will not shake after returning from Reports.
Bug 2: Bottom tab on LHN will not move after saving search.

Actual Result:

Bug 1: Report view shakes after returning from Reports.
Bug 2: Bottom tab on LHN moves after saving search.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6761288_1741130304312.Bug_1.mp4

Bug6761288_1741130286300.Bug_2.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @RachCHopkins

[melvin-bot]

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

[melvin-bot]

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

[mollfpr]

I can't reproduce the bug 1.

I can reproduce it, and I see that the RHN panel is shown for a brief moment. I believe this is related to the current implementation of HelpPanel.

[blazejkustra]

I see that the RHN panel is shown for a brief moment.

Do you mean RHP? Could you guide me on where this RHN/RHP is displayed? I can't reproduce it 🤔

I believe this is related to the current implementation of HelpPanel.

Currently, I don't see a connection between this bug and the HelpPanel. Could you explain why you think they might be related?

[mollfpr]

Do you mean RHP? Could you guide me on where this RHN/RHP is displayed? I can't reproduce it 🤔

Yes! I can reproduce bug 1 with a report that has messages.

Screen.Recording.2025-03-05.at.23.05.50.mp4

For the bug 2, I'm not pretty sure is the new RHP is causing it, but let me try it again.

[blazejkustra]

Yes! I can reproduce bug 1 with a report that has messages.

Am I doing something wrong?

Screen.Recording.2025-03-06.at.15.10.12.mov

[mollfpr]

Could you try to zoom in/out the window?

Screen.Recording.2025-03-06.at.22.09.42.mp4

[blazejkustra]

@mollfpr Still no luck, I can't reproduce on Arc (chromium)

[mollfpr]

I can't repro both bugs 1 & 2.

Screen.Recording.2025-03-10.at.10.59.33.mp4

Asking QA to retest!

[izarutskaya]

We still can repro 1 bug

Recording.3015.mp4

[melvin-bot]

@mollfpr, @RachCHopkins Whoops! This issue is 2 days overdue. Let's get this updated quick!

[melvin-bot]

@mollfpr Eep! 4 days overdue now. Issues have feelings too...

[mollfpr]

Any update @blazejkustra?

[blazejkustra]

Looking into it today, I'll update later 👀

[blazejkustra]

I can finally reproduce this!

before.mov

[blazejkustra]

@mollfpr PR is ready! Thank you for your patience 🙇

[mananjadhav]

@blazejkustra @mollfpr I am assigned as a reviewer, should I review and test this?

[mananjadhav]

I have reviewed and tested the PR.

[blazejkustra]

Thank you @mananjadhav! PR got merged and we can slowly close this issue 😄

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.19-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• Fix report view shakes after returning from Reports #58994

If no regressions arise, payment will be issued on 2025-04-03. 🎊

For reference, here are some details about the assignees on this issue:

• @mananjadhav requires payment through NewDot Manual Requests
• @blazejkustra does not require payment (Contractor)

[melvin-bot]

@mananjadhav @RachCHopkins @mananjadhav The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

[mananjadhav]

BugZero Checklist:

• [Contributor] Classify the bug:

Bug classification

Source of bug:

• 1a. Result of the original design (eg. a case wasn't considered)
• 1b. Mistake during implementation
• 1c. Backend bug
• 1z. Other:

Where bug was reported:

• 2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
• 2b. Reported on staging (eg. found during regression or PR testing)
• 2d. Reported on a PR
• 2z. Other:

Who reported the bug:

• 3a. Expensify user
• 3b. Expensify employee
• 3c. Contributor
• 3d. QA
• 3z. Other:

• [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

  Link to comment: Initial implementation of the Side Pane #56490 (comment)

• [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

  Link to discussion: NA

• [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

I don't think we need a regression test on this one. @mollfpr While the issue says not reproducible on Production I was able to, hence I tagged it as production in the checklist.

@RachCHopkins This is ready for payout.

[RachCHopkins]

Payment Summary:

• Contributor: @blazejkustra no payment due to being a contractor
• Contributor+: @mananjadhav to be paid $250 via NewDot Manual Requests

No upwork job

[RachCHopkins]

Ready to pay @mananjadhav

[garrettmknight]

$250 approved for @mananjadhav