[HOLD for payment 2024-07-10] [$250] Chat - 1:1 DM refreshes itself, composer + action menu closes

[m-natarajan]

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

---

Bug was found when validating #43307
Version Number: 9.0.2-0
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:

Action Performed:

1. Open the app
2. Log in with a new Gmail account
3. Tap on FAB - Start chat
4. Enter a Gmail address that doesn't have an account yet
5. Tap on the account
6. Tap on the "+" button next to the composer

Expected Result:

I should be able to use the + menu and the chat shouldn't refresh itself.

Actual Result:

Chat - 1:1 DM resreshes itself for a few times after opening. Composer + action menu closes and the chat starts refreshing again. The menu is inaccessible.

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6524795_1719377257496.az_recorder_20240626_063343.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~0129f8c701589e31b8
• Upwork Job ID: 1806096676893409978
• Last Price Increase: 2024-06-26

Issue Owner

Current Issue Owner: @Christinadobrzyn

[melvin-bot]

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

[melvin-bot]

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

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

[m-natarajan]

@Christinadobrzyn FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

[m-natarajan]

We think that this bug might be related to #vip-vsb

[Christinadobrzyn]

@arosiclair @roryabraham @c3024 - can you double-check if this relates to #43307

[Christinadobrzyn]

I'm able to reproduce the bug in the OP

screenRecording-26-6-2024-16-5.mp4

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~0129f8c701589e31b8

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @getusha (External)

[pecanoro]

I am not sure if it's the same RCA, but I am getting something similar and I can't send any messages at all: https://expensify.slack.com/archives/C049HHMV9SM/p1719413599651529

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[Christinadobrzyn]

Asking if this is the same as #44419

[arosiclair]

Looks like we're fixing this here: #44544
Slack thread: https://expensify.slack.com/archives/C049HHMV9SM/p1719475873244049

[mountiny]

confirmed its fixed by #44544 gonna add it to the list of issue it fixes

[mountiny]

CPed to staging, confirmed this is fixed 🎉

RPReplay_Final1719507460.mp4

[mountiny]

We will handle C+ payment on the other linked issue, we can close this one now

[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.0.3-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [CP Staging] Add freezeScreenWithLazyLoading function #44544

If no regressions arise, payment will be issued on 2024-07-10. 🎊

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

• @getusha requires payment through NewDot Manual Requests

[melvin-bot]

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

• [@getusha] The PR that introduced the bug has been identified. Link to the PR:
• [@getusha] 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:
• [@getusha] A discussion in #expensify-bugs 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:
• [@getusha] Determine if we should create a regression test for this bug.
• [@getusha] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
• [@Christinadobrzyn] Link the GH issue for creating/updating the regression test once above steps have been agreed upon: