Repository navigation
[HOLD for payment 2024-11-22] [$250] Search - Not here page appears when selecting a non-existing user and then going online #51651
Description
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.55-1
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/5140184
Email or phone of affected tester (no customers): applausetester+bm176@applause.expensifail.com
Issue reported by: Applause - Internal Team
Action Performed:
- Go to https://staging.new.expensify.com/
- Go offline
- Click on the search icon at the top right
- Search for a non-existing user
- Click on the search result
- Go online
Expected Result:
Not here page should not appear, and the chat with the non-existing user should remain visible
Actual Result:
Not here page appears when going online, which contradicts the behavior when performing these steps while online
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
Bug6649175_1730198793234.1.mp4
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~021851703015510861438
- Upwork Job ID: 1851703015510861438
- Last Price Increase: 2024-10-30
- Automatic offers:
- dukenv0307 | Contributor | 104740405
- NJ-2020 | Contributor | 104800732
Activity
melvin-bot commentedon Oct 29, 2024
Triggered auto assignment to @isabelastisser (
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.lanitochka17 commentedon Oct 29, 2024
@isabelastisser FYI 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
lanitochka17 commentedon Oct 29, 2024
We think that this bug might be related to #wave-control
NJ-2020 commentedon Oct 29, 2024
Same RCA as #51473
[-]Search - Not here page appears when selecting a non-existing user and then going online[/-][+][$250] Search - Not here page appears when selecting a non-existing user and then going online[/+]melvin-bot commentedon Oct 30, 2024
Job added to Upwork: https://www.upwork.com/jobs/~021851703015510861438
melvin-bot commentedon Oct 30, 2024
Triggered auto assignment to Contributor-plus team member for initial proposal review - @mkhutornyi (
External)isabelastisser commentedon Oct 30, 2024
Heads up, I will be OOO from Oct 31 until Nov 4, so please re-apply the Bug label and assign a new member if needed. Thanks!
28 remaining items
melvin-bot commentedon Nov 15, 2024
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Nov 15, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.62-4 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 2024-11-22. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Nov 15, 2024
@dukenv0307 @isabelastisser @dukenv0307 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]
isabelastisser commentedon Nov 22, 2024
Payment summary:
Payment made in Upwork to @NJ-2020 - contributor $250
@dukenv0307, payment pending in NewDot - $250 C+.
dukenv0307 commentedon Nov 25, 2024
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[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: https://github.com/Expensify/App/pull/51093/files#r1855741040
[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: N/A
[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. Yes
[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
Test:
Do we agree 👍 or 👎
dukenv0307 commentedon Nov 25, 2024
Hey @isabelastisser I'll request payment via NewDot.
isabelastisser commentedon Nov 25, 2024
Payment summary.
isabelastisser commentedon Nov 25, 2024
All set!
JmillsExpensify commentedon Dec 5, 2024
$250 approved for @dukenv0307