Report field - Show violation on single transaction expense reports #46215
Description
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:
- Workspace is under Control plan.
- Report fields feature is enabled.
- Text type report field is added and it has no initial value.
- The workspace has no unsettled expense.
- Go to staging.new.expensify.com
- Go to workspace chat.
- Submit a manual expense.
- Go to expense report.
- Note that report field violations do not show up.
- Submit another manual expense.
- Note that report field violation shows up.
- Go to Troubleshoot > Clear cache and restart > Reset and restart.
- Go to expense report.
- Note that report field violations disappear..
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?
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop