mWeb - Chat - Black screen after deleting first message

[kbecciv]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Action Performed:

1. Go to URL https://staging.new.expensify.com/
2. Navigate to a conversation (conversation is not very long) in the main testing device
3. Scroll up a bit and choose the first of several messages you already sent back-to-back
4. Verify the chat header with your name appears only appears on your first message
5. Hover over that first message (Web/Desktop) / Tap and hold (Mobile) to view the action menu
6. Click/Tap on the Trash icon to delete the message
7. Verify the message is deleted from the conversation history

Expected Result:

The user deleted the required message without problems.

Actual Result:

Users should be able to delete owned messages, but after deleting first message, the conversation scrolls to the beginning and user sees black screen.

Workaround:

Unknown

Platforms:

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

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.3.10.2

Reproducible in staging?: Yes

Reproducible in production?: No

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

Notes/Photos/Videos: Any additional supporting documentation

az_recorder_20230505_075039.1.mp4

Bug6043764_Screen_Recording_20230505_154529_Chrome.1.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

[OSBotify]

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

[melvin-bot]

Triggered auto assignment to @Beamanator (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[kbecciv]

Issue is not reproductible in Production, attached the video.

Screen.Recording.20230505.164629.Chrome.mp4

[roryabraham]

@kbecciv since I've yet to reproduce this, logs could be very helpful in helping us diagnose this. If you're still able to reproduce it, can you try to capture console logs? Here are some instructions on capturing console logs from a physical device on Android mWeb.

[roryabraham]

I'm not able to reproduce this.

[roryabraham]

Asked for a retest in slack: https://expensify.slack.com/archives/C9YU7BX5M/p1683307443300569

[marcaaron]

Is it exclusive to Android Chrome? What account did we use to reproduce this? @kbecciv

[marcaaron]

Tried and also can’t reproduce this once. Just tried on Android web (emulator)