Skip to content

[HOLD for payment 2023-06-29] [$1000] Delete popup is stuck and screen blinks for few seconds when user tries to delete a message and user gets removed from workspace at that instance #17846

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. Open the app on any device and login with user A
  2. Open the app on any other device and login with user B (ensure that user A is present in one of the workspace to which user B is admin)
  3. On user A device, open workspace to which user B is admin
  4. On user A device, right click or long press on any of the self message and click on delete message to open delete confirmation popup
  5. From user B device, remove user A from that workspace
  6. Observe on user A device, when user B removes user A from workspace, chat blinks by showing not access page, chat page and again not access page and also the delete popup is still open

Expected Result:

App should also close all the popups open on user A device when user B remove user A from workspace. App should also not blink the #announce chat for user A when user B removes user A from workspace

Actual Result:

App keeps the delete popup open even though user A is no longer able to able that chat. App also blinks the chat few times before displaying 'You don't have access' screen

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

delete.popup.remains.open.on.workspace.remove.mp4
Recording.323.mp4

Expensify/Expensify Issue URL:
Issue reported by: @dhanashree-sawant
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1682176575452809

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~019ed03865c0010a59
  • Upwork Job ID: 1651681139754299392
  • Last Price Increase: 2023-06-09

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Apr 23, 2023
  2. MelvinBot commented on Apr 23, 2023

    @MelvinBot
    Contributor

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

  3. MelvinBot commented on Apr 23, 2023

    @MelvinBot
    Contributor

    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. alexpensify commented on Apr 24, 2023

    @alexpensify
    Contributor

    I'll try to test soon.

  5. MelvinBot commented on Apr 26, 2023

    @MelvinBot
    Contributor

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

  6. alexpensify commented on Apr 26, 2023

    @alexpensify
    Contributor

    This one is still on my radar to test.

  7. alexpensify commented on Apr 26, 2023

    @alexpensify
    Contributor

    I'm able to replicate

    2023-04-26_15-08-22

    2023-04-26_15-08-40

  8. MelvinBot commented on Apr 26, 2023

    @MelvinBot
    Contributor

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

  9. alexpensify commented on Apr 26, 2023

    @alexpensify
    Contributor

    @bondydaa - I think we take this to the room to identify how it should function but let me know if you have ideas then we assign it to External. Thanks!

  10. 114 remaining items

  11. melvin-bot commented on Jun 22, 2023

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.30-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2023-06-29. 🎊

    After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

    • External issue reporter
    • Contributor that fixed the issue
    • Contributor+ that helped on the issue and/or PR

    As a reminder, here are the bonuses/penalties that should be applied for any External issue:

    • Merged PR within 3 business days of assignment - 50% bonus
    • Merged PR more than 9 business days after assignment - 50% penalty
  12. melvin-bot commented on Jun 22, 2023

    @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:

    • [@0xmiroslav] The PR that introduced the bug has been identified. Link to the PR:
    • [@0xmiroslav] 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:
    • [@0xmiroslav] 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:
    • [@0xmiroslav] Determine if we should create a regression test for this bug.
    • [@0xmiroslav] 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.
    • [@alexpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
  13. alexpensify commented on Jun 22, 2023

    @alexpensify
    Contributor

    @dhanashree-sawant, @hellohublot, and @0xmiroslav please apply at https://www.upwork.com/jobs/~01522d777e8a7b8f13 and I can prepare for the pay period on 6/29. Thank you!

    Also, @0xmiroslav please let me know if there are any required actions from me for the checklist. Thank you!

  14. dhanashree-sawant commented on Jun 22, 2023

    @dhanashree-sawant

    Hi @alexpensify, should I also apply for reporting bonus?

  15. alexpensify commented on Jun 22, 2023

    @alexpensify
    Contributor

    @dhanashree-sawant - yes please!

  16. dhanashree-sawant commented on Jun 22, 2023

    @dhanashree-sawant

    Thanks, I have applied.

  17. alexpensify commented on Jun 28, 2023

    @alexpensify
    Contributor

    Tomorrow is the payment date. @dhanashree-sawant, @hellohublot, and @0xmiroslav please apply at https://www.upwork.com/jobs/~01522d777e8a7b8f13 Thank you!

  18. dhanashree-sawant commented on Jun 29, 2023

    @dhanashree-sawant

    Thanks @alexpensify , if possible, can you send me invite to the job?

  19. alexpensify commented on Jun 29, 2023

    @alexpensify
    Contributor

    @dhanashree-sawant, @hellohublot, and @0xmiroslav - the proposals have been prepared in Upwork. Please accept and I can complete the payment. Thank you!

  20. dhanashree-sawant commented on Jun 30, 2023

    @dhanashree-sawant

    Thanks a lot! I have accepted the offer.

  21. 0xmiroslav commented on Jun 30, 2023

    @0xmiroslav
    Contributor

    BZ checklist:
    No regressions. This is rare case and so easily missed during initial implementation of popups on report action item.
    I don't think it's worthy of adding regression test step.

  22. alexpensify commented on Jun 30, 2023

    @alexpensify
    Contributor

    Alright, @dhanashree-sawant, @hellohublot, and @0xmiroslav have been paid via Upwork. I've closed the job too, great work here!

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