-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HOLD for payment 2024-07-25] [$250] Expense - Tapping back button after deleting expense leads to not here page #44199
Comments
Triggered auto assignment to @CortneyOfstad ( |
Triggered auto assignment to @youssef-lr ( |
👋 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:
|
@CortneyOfstad 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 |
We think that this bug might be related to #wave-collect - Release 1 |
Job added to Upwork: https://www.upwork.com/jobs/~0149255b2b8a3385dc |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @allroundexperts ( |
@bernhardoj is your fix going to work here too? |
I think we can demote this issue at this point. Its not blocking the user from using the app further, its quite specific edge case too |
Asked @cdOut to look into this as he worked on the details revamp |
@mountiny sorry, which one? |
I fixed the issue. I came from Upwork. Should I submit the proposal, or is there no need to now? |
If I am understanding this correctly, it seems to me that they are basically the same problem and the fix applied here was incomplete. Your proposal is even in the same line as the PR in this issue changed and it's in the same flow. @youssef-lr, @allroundexperts what do you think? |
This is not the same. Previously, we were redirected to the page that was not found. Now, it briefly shows the not found page, when closing the RHP (but finally we are on the correct chat, previously we landed on not found). I'm not sure how we missed it during the testing and review. The RCA here sounds correct. I can have a look at this, but I will probably have some results tomorrow, as I'm finishing my work for today soon. |
Demoting again from this convo |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.8-6 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-07-25. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
@allroundexperts can you have the checklist completed before EOD tomorrow? This will help avoid any delay in payment — thank you! |
Payment Summary
BugZero Checklist (@CortneyOfstad)
|
@allroundexperts please complete the check list at your earliest convenience! Thank you! |
Hi, I just wanted to confirm, has this issue been properly fixed by this or another issue PR or are there still problems as pointed in this previous comment? |
The other issue was closed and fix was added here. |
Checklist
Regression test
Verify that the app returns to the main page. Do we 👍 or 👎 ? |
Payment Summary@allroundexperts — to be paid $250 via NewDot Regression Test |
$250 approved for @allroundexperts |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 9.0.1-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:
Expected Result:
App will return to the main page.
Actual Result:
App shows long skeleton loading and then not here page loads.
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Bug6521360_1719047106407.RPReplay_Final1719038925.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @CortneyOfstadThe text was updated successfully, but these errors were encountered: