Skip to content

mWeb - Chat - When opening a request and going back, the requests list is displayed empty #39609

Closed

Description

@izarutskaya

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


Version Number: v 1.4.60-1
Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers): bellicoignacio@gmail.com
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team

Action Performed:

  1. Open the https://staging.new.expensify.com
  2. Open any chat that contains requests.
  3. Tap on the requests preview.
  4. Open any request from the list displayed.
  5. Tap on the arrow on the top left corner.
  6. Check the requests list behaviour.
  • Sometimes you need to relog-in to see the issue

Expected Result:

The requests list, should remain visible when opening one and returning to previous page.

Actual Result:

After opening one request and tapping on the arrow to go back to previous page, the requests list is displayed empty.

Workaround:

Unknown

Platforms:

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

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6437555_1712204086223.Requests.mp4

Bug6437555_1712204086303!Requests

View all open jobs on GitHub

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Apr 4, 2024
  2. melvin-bot commented on Apr 4, 2024

    @melvin-bot

    Triggered auto assignment to @luacmartins (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  3. melvin-bot commented on Apr 4, 2024

    @melvin-bot

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

  4. github-actions commented on Apr 4, 2024

    @github-actions
    Contributor

    👋 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.
  5. izarutskaya commented on Apr 4, 2024

    @izarutskaya
    Author

    @miljakljajic I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

  6. izarutskaya commented on Apr 4, 2024

    @izarutskaya
    Author

    Production

    Screen_Recording_20240404_170111_Chrome.mp4
  7. izarutskaya commented on Apr 4, 2024

    @izarutskaya
    Author

    We think this issue might be related to the #vip-vsb.

  8. mountiny commented on Apr 4, 2024

    @mountiny
    Contributor

    cc @NikkiWines as it might be still related to the one transaction view

    Noting that the production deploy did not work this morning so the current production is actually 2 releases back from current staging (hence the one transaction PR is not in production yet)

  9. 8 remaining items

  10. luacmartins commented on Apr 8, 2024

    @luacmartins
    Contributor

    PR is in review.

  11. melvin-bot commented on Apr 15, 2024

    @melvin-bot

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

  12. melvin-bot commented on Apr 17, 2024

    @melvin-bot

    @luacmartins, @miljakljajic Eep! 4 days overdue now. Issues have feelings too...

  13. melvin-bot commented on Apr 19, 2024

    @melvin-bot

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

  14. melvin-bot commented on Apr 23, 2024

    @melvin-bot

    @luacmartins, @miljakljajic 10 days overdue. Is anyone even seeing these? Hello?

  15. melvin-bot commented on Apr 25, 2024

    @melvin-bot

    @luacmartins, @miljakljajic 12 days overdue now... This issue's end is nigh!

  16. melvin-bot commented on Apr 29, 2024

    @melvin-bot

    This issue has not been updated in over 14 days. @luacmartins, @miljakljajic eroding to Weekly issue.

  17. melvin-bot commented on May 23, 2024

    @melvin-bot

    This issue has not been updated in over 15 days. @luacmartins, @miljakljajic 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!

  18. luacmartins commented on Jun 27, 2024

    @luacmartins
    Contributor

    This was fixed a while ago, but the automation didn't close the issue. Closing!

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringMonthlyKSv2ReviewingHas a PR in review

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions