-
Notifications
You must be signed in to change notification settings - Fork 3k
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-06-13] [$250] IOU - RBR is present in LHN but no error msg in combined report when deleting paid IOU offline #39689
Comments
Triggered auto assignment to @alexpensify ( |
Triggered auto assignment to @madmax330 ( |
👋 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:
|
@alexpensify 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 this issue might be related to the #collect project. |
Production bandicam.2024-04-05.11-47-52-412.mp4 |
This is a specific and rare flow so I dont think we have to hold the deploy on this one. This is related to the combined view cc @NikkiWines I think we can make this external |
Job added to Upwork: https://www.upwork.com/jobs/~01ebfa7c151ee18ff6 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @abdulrahuman5196 ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.IOU - RBR is present in LHN but no error msg in combined report when deleting paid IOU offline. What is the root cause of that problem?When a receipt error occurs, it will be logged within the With the recent introduction of the single transaction view, in scenarios involving only one money request, there won't be an IOU report generated. Therefore, any receipt errors and prompts to download associated files will not be displayed. What changes do you think we should make in order to solve the problem?Add Below mention code here
To get the receipt error from the
and replace line# 266 with below code:
Video:https://drive.google.com/file/d/1L8UHfYOTKoEBsSxGtQ_aZSGoFZ4mS5wy/view?usp=sharing |
@abdulrahuman5196 when you get a chance, can you review the proposals here? Thanks! |
Hi, Will check on the proposals today |
@abdulrahuman5196 PR submitted |
Weekly Update: The PR is moving along through the review process. |
Weekly Update: The PR is going through a recent round of reviews. |
Weekly Update: The PR is under the last reviews |
Heads up, I will be offline until Tuesday, May 28, 2024, and will not actively watch over this GitHub during that period.If anything urgent is needed here, please ask for help in the #expensify-open-source Slack Room-- thanks! |
@madmax330 we need a review in this PR: #40460 (comment) @abdulrahuman5196 - I'm going to lean on engineering feedback here. Thanks! |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.79-11 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-06-13. 🎊 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:
|
@kaushiktd - you didn't get an offer since the automation failed here: #39689 (comment) I'll need to manually create a new request in Upwork before the payment due date. When it's ready, I'll reply here. |
Thank you @alexpensify. Earlier I was able to receive an offer on my Upwork from Melvin but it stopped for the last couple of months. Do you have any idea what can be an issue? |
I don't know about a couple of months ago, the issue that I'm describing today is a recent one. Either way, it's on my radar and I'll deal with it manually. I'll have an update early next week because the payment date is 2024-06-13. |
Ok, ready for the payment process in Upwork. @kaushiktd - I've created a new Upwork job, please accept here: https://www.upwork.com/jobs/~01bce135ee5dd897fc Thanks! |
Offer accepted on Upwork @alexpensify |
Paid via Upwork!Payouts due: 2024-06-13
Upwork job is here |
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: 1.4.60-5
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4476117
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team
Action Performed:
Precondition:
Expected Result:
The error "Unexpected error deleting the money request, please try again later" should be present in one transaction report view.
Actual Result:
There is RBR for one transaction report in LHN, but there is no error in the report itself.
This issue happens when there is only one request.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Bug6438412_1712261176833.20240405_035838.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @alexpensifyThe text was updated successfully, but these errors were encountered: