You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Dupe detection - Confirmation page RHP turns to not here page while dismissing #46179
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:
Go to staging.new.expensify.com
Go to workspace chat.
Submit two same expenses (same amount and merchant).
Go to transaction thread of any expense.
Click Review duplicates.
Select Keep this one (any).
Proceed to confirmation page.
Click outside the RHP to dismiss.
Note that RHP turns to not here page while dismissing.
Repeat Step 5 to 7.
Click Confirm button.
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?
👋 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:
Identify the pull request that introduced this issue and revert it.
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!
Activity
melvin-bot commentedon Jul 25, 2024
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 commentedon Jul 25, 2024
Triggered auto assignment to @flodnv (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Jul 25, 2024
👋 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:
m-natarajan commentedon Jul 25, 2024
We think this bug might be related to #wave-collect - Release 2
gijoe0295 commentedon Jul 25, 2024
Will be resolved in #45965
13 remaining items
melvin-bot commentedon Sep 4, 2024
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 commentedon Sep 5, 2024
#45965 was deployed, we need a retest @jliexpensify @m-natarajan
jliexpensify commentedon Sep 6, 2024
Weird, I am not seeing a
Resolve Duplicatesoption on v0.0.30-7 (staging)@m-natarajan @gijoe0295 can you both verify this/confirm this isn't a bug anymore?
jliexpensify commentedon Sep 18, 2024
Going to close this as I couldn't repro.