Skip to content

[HOLD for payment 2023-10-02] [HOLD for payment 2023-07-24] [$1000] Failed Room Termination: User Continues Chatting in Android App After Leaving Room on Web #21518

Closed

Description

@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. Login with User A ( mobile number) > create a workspace with user B and C
  2. Create a room in public mode
  3. Send the public room link or QR code to User B
  4. Open User B in android as well as Desktop chrome and join the room across web and app using link & QR code
  5. From User B, send messages to the room
  6. From User B, Leave the room from web
  7. Verify if User B can still send messages from android app

Expected Result:

When a user leaves a room on the web version, their participation in the room should be terminated across all platforms, including the Android app. They should not be able to send messages or interact within the room.

Actual Result:

After a user leaves a room on the web version, they can still send messages and participate in the chat room using the Android app. This behaviour contradicts the expected result and allows the user to continue engaging with the room despite their departure on the web.

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.32-5
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

first.web.mp4
second.android.mp4
Recording.871.mp4

Expensify/Expensify Issue URL:
Issue reported by: @avi-shek-jha
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1687048129225459

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~012dc182ad93ca216b
  • Upwork Job ID: 1674172420971741184
  • Last Price Increase: 2023-07-05
  • Automatic offers:
    • wildan-m | Contributor | 27225915
    • avi-shek-jha | Reporter | 27225918

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jun 25, 2023
  2. melvin-bot commented on Jun 25, 2023

    @melvin-bot

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

  3. melvin-bot commented on Jun 25, 2023

    @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
  4. johncschuster commented on Jun 28, 2023

    @johncschuster
    Contributor

    Working on reproducing this behavior this afternoon.

  5. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Jun 28, 2023
  6. changed the title [-]Failed Room Termination: User Continues Chatting in Android App After Leaving Room on Web[/-] [+][$1000] Failed Room Termination: User Continues Chatting in Android App After Leaving Room on Web[/+] on Jun 28, 2023
  7. melvin-bot commented on Jun 28, 2023

    @melvin-bot
  8. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jun 28, 2023
  9. melvin-bot commented on Jun 28, 2023

    @melvin-bot

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

  10. melvin-bot commented on Jun 28, 2023

    @melvin-bot

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

  11. 128 remaining items

  12. removed
    Help WantedApply this label when an issue is open to proposals by contributors
    on Oct 16, 2023
  13. melvin-bot commented on Oct 16, 2023

    @melvin-bot

    📣 @wildan-m 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!

    Offer link
    Upwork job
    Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑‍💻
    Keep in mind: Code of Conduct | Contributing 📖

  14. melvin-bot commented on Oct 16, 2023

    @melvin-bot

    📣 @avi-shek-jha 🎉 An offer has been automatically sent to your Upwork account for the Reporter role 🎉 Thanks for contributing to the Expensify app!

    Offer link
    Upwork job

  15. johncschuster commented on Oct 16, 2023

    @johncschuster
    Contributor

    Ok, the job seems to not want to open back up. I'm going to create an issue just for payment for this. Standby.

  16. johncschuster commented on Oct 16, 2023

    @johncschuster
    Contributor

    @wildan-m can you please go to the linked issue above and comment on it so I can assign it to you? That should get the job offer sent to you correctly.

  17. avi-shek-jha commented on Oct 16, 2023

    @avi-shek-jha

    Hello, as a reporter, I only received an offer for 50 dollars. I am aware of the new policies. But, I reported this on June 17 and the issue was created on June 25 almost 2 months before the new policies took place. Can anyone please send me the offer link with corrected amount of 250 USD?

  18. johncschuster commented on Oct 18, 2023

    @johncschuster
    Contributor

    Hi @avi-shek-jha, thanks for calling that out. I will correct that in Upwork.

  19. johncschuster commented on Oct 18, 2023

    @johncschuster
    Contributor

    @avi-shek-jha, I've corrected that in Upwork. Can you please accept the offer? I'll take care of payment once you've done that.

  20. avi-shek-jha commented on Oct 18, 2023

    @avi-shek-jha

    Thank you John. I appreciate it. I have accepted the offer.

  21. johncschuster commented on Oct 18, 2023

    @johncschuster
    Contributor

    Ok everyone! I'm handling payments on this issue. I'm going to close this one out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions