[Due for payment 2025-05-27] [$250] Settings-Required field error is not displayed when clearing the field

[mitarachim]

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: 9.1.28-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: #56068
Email or phone of affected tester (no customers): agexptest+pr1504@gmail.com
Issue reported by: Applause Internal Team
Device used: Windows 10/ Chrome, Samsung S23FE/ Android 14
App Component: User Settings

Action Performed:

1. Go to https://staging.new.expensify.com/
2. Log in with any Expensify account
3. Go to Settings > Profile
4. Click on Status > Clear after > Custom > Date
5. Choose any date
6. Clear the field
7. Verify that the required field error is displayed
8. Go back
9. Click on Date again
10. Clear the field by clicking the X button twice without closing the date picker

Expected Result:

The required field error is displayed after clearing the field, even when the date picker is open.

Actual Result:

The required field error is not displayed when clearing the field without closing the date picker.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6802380_1744694724631.No_required_field_error.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021917203087848355414
• Upwork Job ID: 1917203087848355414
• Last Price Increase: 2025-05-06
• Automatic offers:
• daledah | Contributor | 107210364

Issue Owner

Current Issue Owner: @

Issue Owner

Current Issue Owner: @lydiabarclay

[melvin-bot]

Triggered auto assignment to @lydiabarclay (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]

Triggered auto assignment to @mollfpr (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 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:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[daledah]

🚨 Edited by proposal-police: This proposal was edited at 2025-04-29 13:09:51 UTC.

Proposal

Please re-state the problem that we are trying to solve in this issue.

The required field error is not displayed when clearing the field without closing the date picker.

What is the root cause of that problem?

Offending PR

This is a hidden bug that only appeared after the offending PR.

When validating error, we only keep the fields that is touched:

App/src/components/Form/FormProvider.tsx

Line 168 in 4ee6daa

const touchedInputErrors = Object.fromEntries(Object.entries(validateErrors).filter(([inputID]) => touchedInputs.current[inputID]));

But when dismissing the date picker, there's no onTouched call:

App/src/components/DatePicker/index.tsx

Lines 72 to 75 in 4ee6daa

	const closeDatePicker = useCallback(() => {
	textInputRef.current?.blur();
	setIsModalVisible(false);
	}, []);

And when clicking clear button, onTouched is called with delay:

App/src/components/Form/FormProvider.tsx

Lines 343 to 345 in 6d6628c

	setTimeout(() => {
	setTouchedInput(inputID);
	}, VALIDATE_DELAY);

While onValidate is called immediately when input change:

App/src/components/Form/FormProvider.tsx

Line 408 in 6d6628c

onValidate(newState);

So when calling onValidate there's no data for the input in the touchedInputs ref, resulting in errors returned empty and no error is shown.

What changes do you think we should make in order to solve the problem?

We should call onTouched when closing modal

App/src/components/DatePicker/index.tsx

Lines 72 to 75 in 6d6628c

	const closeDatePicker = useCallback(() => {
	textInputRef.current?.blur();
	setIsModalVisible(false);
	}, []);

    const closeDatePicker = useCallback(() => {
        textInputRef.current?.blur();
        setIsModalVisible(false);
        onTouched();
    }, [onTouched]);

OR we can add setTouchedInput before onValidate in onInputChange here:

App/src/components/Form/FormProvider.tsx

Lines 407 to 409 in 6d6628c

	if (shouldValidateOnChange) {
	onValidate(newState);
	}

Same as onBlur:

App/src/components/Form/FormProvider.tsx

Lines 385 to 389 in 6d6628c

	setTouchedInput(inputID);
	// We don't validate the form on blur in case the current screen is not focused
	if (shouldValidateOnBlur && isFocusedRef.current) {
	onValidate(inputValues, !hasServerError);
	}

To address this comment, remove shouldShowClearButton in these components:

App/src/pages/GroupChatNameEditPage.tsx

Line 104 in 758691e

shouldShowClearButton

App/src/pages/TripChatNameEditPage.tsx

Line 95 in 758691e

shouldShowClearButton

App/src/pages/Search/SavedSearchRenamePage.tsx

Line 75 in 758691e

shouldShowClearButton

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

None

What alternative solutions did you explore? (Optional)

This logic

App/src/components/Form/FormProvider.tsx

Lines 343 to 345 in 6d6628c

	setTimeout(() => {
	setTouchedInput(inputID);
	}, VALIDATE_DELAY);

was added in this PR to fix this bug. However, I tried removing the timeout and the bug is not reproduced anymore, so we can remove it.

App/src/components/Form/FormProvider.tsx

Lines 343 to 345 in 6d6628c

	setTimeout(() => {
	setTouchedInput(inputID);
	}, VALIDATE_DELAY);

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.