Skip to content

[HOLD for payment 2024-12-05] [HOLD for payment 2024-12-03] [$250] mweb/Chrome - Thread - Not here page when open multi level threads #52204

Closed

Description

@lanitochka17

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: 9.0.59-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5193203&group_by=cases:section_id&group_order=asc&group_id=291935
Issue reported by: Applause - Internal Team

Action Performed:

  1. Navigate to any conversation> Send a message
    2 Reply in the thread of this message
  2. Create a thread within the thread
  3. Repeat steps until you have 5 different levels of threads
  4. Click on the header link to navigate to the parent thread
  5. Go through the threads again

Expected Result:

All thread should open and no error page should appear

Actual Result:

Error page opens when open the last multi level thread/ same behavior occurs while creating multi level threads too

Workaround:

Unknown

Platforms:

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

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence
Bug6657771_1730995176084.Recording__4483.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021855829217876432826
  • Upwork Job ID: 1855829217876432826
  • Last Price Increase: 2024-11-11
Issue OwnerCurrent Issue Owner: @Christinadobrzyn

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Nov 7, 2024
  2. melvin-bot commented on Nov 7, 2024

    @melvin-bot

    Triggered auto assignment to @Christinadobrzyn (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

  3. Christinadobrzyn commented on Nov 8, 2024

    @Christinadobrzyn
    Contributor

    I'm not getting this error. Asking QA for more information on the error

    screenRecording-8-11-2024-13-49.mp4
  4. MelvinBot commented on Nov 8, 2024

    @MelvinBot
    Contributor

    This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

  5. bernhardoj commented on Nov 8, 2024

    @bernhardoj
    Contributor

    This is most likely the same as #51825 (comment) which is easier to repro while offline. Can we reopen that issue or should I move my proposal here?

  6. izarutskaya commented on Nov 8, 2024

    @izarutskaya

    Tester still can reproducible the issue with the same steps
    Build v9.0.59-0

    922ca273-f50f-4268-9c24-775b8645aec8.mp4
  7. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Nov 11, 2024
  8. melvin-bot commented on Nov 11, 2024

    @melvin-bot
  9. changed the title [-]mweb/Chrome - Thread - Not here page when open multi level threads[/-] [+][$250] mweb/Chrome - Thread - Not here page when open multi level threads[/+] on Nov 11, 2024
  10. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Nov 11, 2024
  11. 53 remaining items

  12. melvin-bot commented on Nov 28, 2024

    @melvin-bot

    @hoangzinh @Christinadobrzyn @hoangzinh The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  13. Christinadobrzyn commented on Dec 3, 2024

    @Christinadobrzyn
    Contributor

    BugZero Checklist:

    • [Contributor] Classify the bug:
    Bug classification

    Source of bug:

    • 1a. Result of the original design (eg. a case wasn't considered)
    • 1b. Mistake during implementation
    • 1c. Backend bug
    • 1z. Other:

    Where bug was reported:

    • 2a. Reported on production
    • 2b. Reported on staging (deploy blocker)
    • 2c. Reported on both staging and production
    • 2d. Reported on a PR
    • 2z. Other:

    Who reported the bug:

    • 3a. Expensify user
    • 3b. Expensify employee
    • 3c. Contributor
    • 3d. QA
    • 3z. Other:
    • [Contributor] 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:

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source 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:

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

    Regression Test Proposal Template
    • [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

      Link to issue:

    Regression Test Proposal

    Precondition:

    Test:

    Do we agree 👍 or 👎

  14. Christinadobrzyn commented on Dec 3, 2024

    @Christinadobrzyn
    Contributor

    whoops! sorry for posting ^ @hoangzinh- Let us know about a regression test.

  15. hoangzinh commented on Dec 4, 2024

    @hoangzinh
    Contributor

    @Christinadobrzyn I think we won't need a regression test for this issue. It's an edge-case issue when user creates a new thread while offline, in online case it's hard to reproduce. Btw, I think we already have a regression test somewhere to cover a scenario that creates a new thread.

  16. Christinadobrzyn commented on Dec 4, 2024

    @Christinadobrzyn
    Contributor

    Awesome! thanks @hoangzinh!

    Contributor: @bernhardoj paid $250 via NewDot
    Contributor+: @hoangzinh  owed $250 via NewDot

    Payment day is tomorrow

  17. melvin-bot commented on Dec 5, 2024

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@Christinadobrzyn)

    • I have verified the correct assignees and roles are listed above and updated the neccesary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/1855829217876432826/hired)
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  18. bernhardoj commented on Dec 5, 2024

    @bernhardoj
    Contributor

    Requested in ND.

  19. JmillsExpensify commented on Dec 5, 2024

    @JmillsExpensify
    Contributor

    $250 approved for @bernhardoj

  20. Christinadobrzyn commented on Dec 5, 2024

    @Christinadobrzyn
    Contributor

    @hoangzinh can you please submit a request for payment through NewDot? TY!

  21. hoangzinh commented on Dec 6, 2024

    @hoangzinh
    Contributor

    ah yes. Thanks @Christinadobrzyn. Requested in ND

  22. Christinadobrzyn commented on Dec 6, 2024

    @Christinadobrzyn
    Contributor

    Awesome! TY! Closing!

  23. garrettmknight commented on Dec 12, 2024

    @garrettmknight
    Contributor

    $250 approved for @hoangzinh

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