[HOLD for payment 2024-01-31] [$500] Settings - On clear after never, status save does not work

[kbecciv]

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: v1.4.13-4
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:

1. Open the app
2. If status already set then open the status by clicking besides settings OR set status from settings->profile->status and reopen status page
3. Set 'clear after' to never and save
4. Again open status and make any changes to message or emoji
5. Click on save and observe that now app does nothing

Expected Result:

App should save the status on click on save on status page

Actual Result:

App does nothing on click on save when clear after is set to Never on last save

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

Screenshots/Videos

Add any screenshot/video evidence

Bug6314365_1702637389033.ios_native_-_clear_after_never_save_not_working.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01c57d019eaab2d964
• Upwork Job ID: 1736919348213882880
• Last Price Increase: 2024-01-10
• Automatic offers:
• bernhardoj | Contributor | 28105137

[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.

[melvin-bot]

Triggered auto assignment to @johnmlee101 (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[Julesssss]

FYI, another status bug was raised here. Perhaps both were caused by the same PR

[bernhardoj]

az## Proposal

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

After selecting NEVER as the clear after value and saving it, trying to update the status emoji/message doesn't work anymore.

What is the root cause of that problem?

If we select NEVER as the clear after value, we will save it as an empty string and so does the BE return it as an empty string.

App/src/pages/settings/Profile/CustomStatus/StatusPage.js

Lines 82 to 86 in 6fc070b

	User.updateCustomStatus({
	text: statusText,
	emojiCode,
	clearAfter: clearAfterTime !== CONST.CUSTOM_STATUS_TYPES.NEVER ? clearAfterTime : '',
	});

When we try to update again by changing the emoji/message, it will fail here because clearAfterTime is an empty string.

App/src/pages/settings/Profile/CustomStatus/StatusPage.js

Lines 75 to 80 in 6fc070b

	const clearAfterTime = draftClearAfter || currentUserClearAfter;
	const isValid = DateUtils.isTimeAtLeastOneMinuteInFuture({dateTimeString: clearAfterTime});
	if (!isValid && clearAfterTime !== CONST.CUSTOM_STATUS_TYPES.NEVER) {
	setBrickRoadIndicator(isValidClearAfterDate() ? null : CONST.BRICK_ROAD_INDICATOR_STATUS.ERROR);
	return;
	}

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

We should fall back the value of clearAfterTime to CONST.CUSTOM_STATUS_TYPES.NEVER.

const clearAfterTime = draftClearAfter || currentUserClearAfter || CONST.CUSTOM_STATUS_TYPES.NEVER;

What alternative solutions did you explore? (Optional)

The question that might arise is, why the error message doesn't show? It's because isValidClearAfterDate returns true. In isValidClearAfterDate, we return true if the clear after value is either NEVER or an empty string.

App/src/pages/settings/Profile/CustomStatus/StatusPage.js

Lines 63 to 67 in e2eca1b

	const isValidClearAfterDate = useCallback(() => {
	const clearAfterTime = draftClearAfter || currentUserClearAfter;
	if (clearAfterTime === CONST.CUSTOM_STATUS_TYPES.NEVER || clearAfterTime === '') {
	return true;
	}

So, another way to fix is, return early only if clear after value is not empty.

if (!isValid && clearAfterTime !== '' && clearAfterTime !== CONST.CUSTOM_STATUS_TYPES.NEVER) {

[Pujan92]

Proposal

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

Once we set a status with clear never option, updating status again isn't working

What is the root cause of that problem?

For a clear after Never option we are setting an empty string here.

App/src/pages/settings/Profile/CustomStatus/StatusPage.js

Lines 82 to 86 in 990815f

	User.updateCustomStatus({
	text: statusText,
	emojiCode,
	clearAfter: clearAfterTime !== CONST.CUSTOM_STATUS_TYPES.NEVER ? clearAfterTime : '',
	});

But on mount while setting the draft status we are not using an empty string as Never here.

App/src/pages/settings/Profile/CustomStatus/StatusPage.js

Lines 108 to 113 in 990815f

	useEffect(() => {
	if (!currentUserEmojiCode && !currentUserClearAfter && !draftClearAfter) {
	User.updateDraftCustomStatus({clearAfter: DateUtils.getEndOfToday()});
	} else {
	User.updateDraftCustomStatus({clearAfter: currentUserClearAfter});
	}

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

On mount logic consider an empty string as a value Never for draft custom status bcoz the else block will executes when we have existing status details.

User.updateDraftCustomStatus({clearAfter: currentUserClearAfter || CONST.CUSTOM_STATUS_TYPES.NEVER});

App/src/pages/settings/Profile/CustomStatus/StatusPage.js

Line 112 in 990815f

User.updateDraftCustomStatus({clearAfter: currentUserClearAfter});