mWeb - Chat - "View details" in chat is not responding

[kavimuru]

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 https://staging.expensify.cash
2. Log in with any user
3. Find the user where you have requested money and select the user.
4. Find the "view details" in the conversation and click on it

Expected Result:

"View details" should open and I will be able to see all details

Actual Result:

"View details" isn't responding

Workaround:

Unknown

Platform:

Where is this issue occurring?

Web
iOS
Android
Desktop App
Mobile Web ✔️

Version Number: 1.0.75-0
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

https://user-images.githubusercontent.com/43996225/124005277-e08bf800-d9a6-11eb-9d08-a21d858ff81d.mp4

Expensify/Expensify Issue URL:

View all open jobs on Upwork

[MelvinBot]

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

[parasharrajat]

Regression from #3659.

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

[MelvinBot]

Triggered auto assignment to @michaelhaxhiu (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

[parasharrajat]

This is fixed

[bondydaa]

the external on here since it seems that this is already being handled.

This is from #3659, which is being reverted on #3816.

Viacheslav80 has said they will fix it in a follow up PR so I think we just need to make sure it gets back assigned to them?

[bondydaa]

oh thanks @parasharrajat! can you link us to which PR ended up fixing this? I'm not 100% on the protocol here.

[parasharrajat]

#3816. This revert PR fixed it.

[michaelhaxhiu]

Cool, should we close this?