[HOLD E#326093] [$1000] Chat inconsistency between User A and User B after a Request money

[kavimuru]

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

---

Action Performed:

1. user A login
2. user A creates a money request for user B
3. user B login
4. user B pays request money from user A
5. user A writes a message in the IOU thread with user B, click send
6. user B cannot see the message
7. user B must exit the chat and enter again to be able to see the message sent by user A

Expected Result:

both users should be able to see chat messages the moment they are sent

Actual Result:

both users cannot see the chat messages at the time they are sent, one of the users must exit the chat to update

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 / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.3.49-0
Reproducible in staging?: y
Reproducible in production?: y
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

WhatsApp.Video.2023-08-01.at.22.24.23.mp4

Compartir.pantalla.-.2023-08-01.22_03_22.mp4

Recording.1427.mp4

Expensify/Expensify Issue URL:
Issue reported by: @eusalazar
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1690939247360729

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~0106ee6101f89ce228
• Upwork Job ID: 1691926490954178560
• Last Price Increase: 2023-08-23

Issue Owner

Current Issue Owner: @flodnv

Issue Owner

Current Issue Owner: @flodnv

[melvin-bot]

Triggered auto assignment to @johncschuster (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[melvin-bot]

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

[johncschuster]

I haven't gotten to testing this behavior. I'll work on it this afternoon.

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~0106ee6101f89ce228

[melvin-bot]

Current assignee @johncschuster is eligible for the External assigner, not assigning anyone new.

[melvin-bot]

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

[johncschuster]

Commenting to get Melvin to chill out with the Overdue label.

[Piotrfj]

Hey, I'm Piotr from Callstack - expert contributor group - I would like to help resolve this issue

[melvin-bot]

📣 @Piotrfj! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

1. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
2. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
3. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
   
   Format:

Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>

[melvin-bot]

@johncschuster, @eVoloshchak Eep! 4 days overdue now. Issues have feelings too...

[Piotrfj]

Update: I was able to reproduce the issue. Seems like it could be backend issue, I've checked in websocket and there were no events to add new report.

[melvin-bot]

@johncschuster @eVoloshchak this issue is now 3 weeks old. There is one more week left before this issue breaks WAQ and will need to go internal. What needs to happen to get a PR in review this week? Please create a thread in #expensify-open-source to discuss. Thanks!

[melvin-bot]

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

[melvin-bot]

@johncschuster, @eVoloshchak 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

[melvin-bot]

@johncschuster, @eVoloshchak 10 days overdue. Is anyone even seeing these? Hello?

[johncschuster]

@eVoloshchak do you agree with @Piotrfj that this could be a backend issue? If so, I'll make this internal.

[flodnv]

I can confirm I was able to reproduce this

[johncschuster]

Nice one, @flodnv!

[johncschuster]

No update here

[melvin-bot]

@flodnv, @johncschuster, @eVoloshchak Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[flodnv]

No updates, still focusing on higher priority strategic projects.

[johncschuster]

Thanks for the update, @flodnv! Should we downgrade the label on this one?

[flodnv]

I did that but you undid that last week 😄

[flodnv]

Still no update for now.

[flodnv]

Sorry for the delay. Turns out user B will never receive the pusher update, does not matter how many message there are in the IOU thread, the backend was never sending it, so I fixed that 🙃 PR is in review...

[mountiny]

I will put this on hold for internal issue https://github.com/Expensify/Expensify/issues/326093

[melvin-bot]

This issue has not been updated in over 15 days. @flodnv, @johncschuster, @eVoloshchak eroding to Monthly issue.

P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

[melvin-bot]

@flodnv, @johncschuster, @eVoloshchak, this Monthly task hasn't been acted upon in 6 weeks; closing.

If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead.