Dupe detection - Confirmation page RHP turns to not here page while dismissing

[m-natarajan]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Found when validating #45877
Version Number: 9.0.12.0
Reproducible in staging?: y
Reproducible in production?: n
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
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Submit two same expenses (same amount and merchant).
4. Go to transaction thread of any expense.
5. Click Review duplicates.
6. Select Keep this one (any).
7. Proceed to confirmation page.
8. Click outside the RHP to dismiss.
9. Note that RHP turns to not here page while dismissing.
10. Repeat Step 5 to 7.
11. Click Confirm button.
12. Note that RHP turns to not here page while dismissing.

Expected Result:

In Step 9 and 12, the confirmation page will not turn to not here page while dismissing.

Actual Result:

In Step 9 and 12, the confirmation page turns to not here page while dismissing.

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

Bug6552268_1721883182475.20240725_124913.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @jliexpensify

[melvin-bot]

Triggered auto assignment to @jliexpensify (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.

[melvin-bot]

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

[github-actions]

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

[m-natarajan]

We think this bug might be related to #wave-collect - Release 2

[gijoe0295]

Will be resolved in #45965

[roryabraham]

Dupe detection is behind a beta, so NAB

[melvin-bot]

@flodnv, @jliexpensify, @gijoe0295 Whoops! This issue is 2 days overdue. Let's get this updated quick!

[melvin-bot]

@flodnv, @jliexpensify, @gijoe0295 Eep! 4 days overdue now. Issues have feelings too...

[jliexpensify]

Could we switch this to Weekly or Monthly since it's behind a beta and will resolved by #45965? (and to stop the pings?)

[melvin-bot]

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

[flodnv]

#45965 was deployed, we need a retest @jliexpensify @m-natarajan

[jliexpensify]

Weird, I am not seeing a Resolve Duplicates option on v0.0.30-7 (staging)

@m-natarajan @gijoe0295 can you both verify this/confirm this isn't a bug anymore?

[jliexpensify]

Going to close this as I couldn't repro.