Repository navigation
Report field - Show violation on single transaction expense reports #46215
Description
Activity
Triggered auto assignment to @AndrewGable (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.Triggered auto assignment to @kadiealexander (
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.👋 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.
- Find someone who can quickly fix the issue.
- Fix the issue yourself.
@thienlnam @jnowakow @war-in @blazejkustra @allroundexperts - Can you check into this?
9 remaining items
I think I found the cause of the issue: #46425
When the first expense was created we dealt with an optimistic IOU report and there was no
fieldListfield in it. If thefieldListis undefined we can't tell which fields were violated.I added
fieldListto theOptimisticIOUReportandOptimisticExpenseReporttypes. That way we can optimistically setfieldList🎉I'll mark PR as ready for review tomorrow because I need to test it and record videos
Reacted by Jack NamPR is ready for C+ review :)
This issue has not been updated in over 15 days. @thienlnam, @kadiealexander, @war-in 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!
Can I get assigned here since I reviewed the PR?
My bad. This can be closed. You're correct @thienlnam
Reacted by Jack Nam
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Found when validating #44139
Version Number: 9.0.12.0
Reproducible in staging?: y
Reproducible in production?: no
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:
Precondition:
Expected Result:
In Step 5, report field violation will show up after submitting the first expense.
In Step 10, report field violation will persist after clearing cache and restarting app.
Actual Result:
In Step 5, report field violation does not show up after submitting the first expense.
It only shows up after submitting the second expense (Step 7).
In Step 10, report field violation disappears after clearing cache and restarting app.
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Bug6552777_1721919071237.20240725_224410.mp4
View all open jobs on GitHub