fix: The Back and error dismiss buttons do not respond when adding existing account

[etCoderDysto]

Explanation of Change

Fixed Issues

$ #72754
PROPOSAL: #72754 (comment)

Tests

• Verify that no errors appear in the JS console

Offline tests

none

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."
Test 1

1. Navigate to Account Settings > Profile > Contact Methods
2. Select "New Contact Method."
3. Enter an already registered email
4. Enter the correct magic code
5. Tap on close button
6. Verify that the error is cleared

Test 2

1. Navigate to Account Settings > Profile > Contact Methods
2. Select "New Contact Method."
3. Enter an already registered email
4. Enter the correct magic code
5. Tap on back button
6. Verify that you are navigated back

Test 3

1. Navigate to Account Settings > Profile > Contact Methods
2. Select "New Contact Method."
3. Enter an already registered email
4. Enter the correct magic code
5. Clear the magic code
6. Verify that the error message is cleared

Test 4

1. Navigate to Account Settings > Profile > Contact Methods
2. Select "New Contact Method."
3. Enter a new email
4. Enter the correct magic code
5. Enter a correct magic code sent to the newly added contact method
6. Verify that the contact method is added successfully

Test 5

1. Go to Setting
2. Security
3. Add copilot
4. Select User
5. Select Access Level
6. Click Add copilot
7. Request magic code until “Failed to send a new magic code. Please wait a bit and try again.” Error is displayed
8. Click on close button
9. Verify that the error is cleared

Test 6
Precondition: You have added a copilot

1. Go to Setting
2. Go to Security
3. Add copilot
4. Click on the copilot
5. Click on Change access level
6. Request magic code until “Failed to send a new magic code. Please wait a bit and try again.” error is displayed
7. Click on close button
8. Verify that the error is cleared

Test 7
Precondition: You have set up Expensify card

1. Go to a workspace settings
2. Go to Expensify card
3. Select any card type
4. Fill all required fields until you reach the verification page
5. Request magic code until “Failed to send a new magic code. Please wait a bit and try again.” error is displayed
6. Click on close button
7. Verify that the error is cleared

• Verify that no errors appear in the JS console

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I verified there are no new alerts related to the canBeMissing param for useOnyx
• I followed proper code patterns (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
  • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
• I verified that if a function's arguments changed that all usages have also been updated correctly
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
• If new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

android.Screen.Recording.2025-10-24.at.7.52.43.in.the.morning.mp4

Android.Screen.Recording.2025-10-29.at.8.08.07.in.the.evening.mp4

Android: mWeb Chrome

android.chrome.Screen.Recording.2025-10-24.at.7.49.13.in.the.morning.mp4

android.chrome.Screen.Recording.2025-10-29.at.8.06.03.in.the.evening.mp4

iOS: Native

ios.Screen.Recording.2025-10-23.at.9.55.56.at.night.mp4

ios.Screen.Recording.2025-10-29.at.7.53.29.in.the.evening.mp4

iOS: mWeb Safari

ios.safari.Screen.Recording.2025-10-23.at.10.00.51.at.night.mp4

safari.Screen.Recording.2025-10-29.at.7.57.34.in.the.evening.mp4

MacOS: Chrome / Safari

Screen.Recording.2025-10-29.at.4.18.27.in.the.afternoon.mp4

web.Screen.Recording.2025-10-29.at.4.21.34.in.the.afternoon.mp4

MacOS: Desktop

desktiop.Screen.Recording.2025-10-23.at.9.30.46.at.night.mp4

Desktop.Screen.Recording.2025-10-29.at.7.49.05.in.the.evening.mp4

[melvin-bot]

@dukenv0307 Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

[etCoderDysto]

@dukenv0307 clearPendingContactActionErrors is not used anywhere in the code base. Should I remove it?

App/src/libs/actions/User.ts

Lines 346 to 350 in bd83ec9

	function clearPendingContactActionErrors() {
	Onyx.merge(ONYXKEYS.PENDING_CONTACT_ACTION, {
	errorFields: null,
	});
	}

[etCoderDysto]

BUG: Close button doesn't work when failed to send a magic code error message is displayed

1. Click New contact method
2. Add email
3. Request magic code until Failed to send a magic code error message is displayed
4. Click close button on the error message

Screen.Recording.2025-10-23.at.10.15.59.at.night.mov

Should fix it here?

[codecov]

Codecov Report

❌ Patch coverage is 50.00000% with 1 line in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
...ionModal/ValidateCodeForm/BaseValidateCodeForm.tsx	50.00%	1 Missing ⚠️

Files with missing lines	Coverage Δ
.../Contacts/NewContactMethodConfirmMagicCodePage.tsx	0.00% <ø> (ø)
...ionModal/ValidateCodeForm/BaseValidateCodeForm.tsx	83.05% <50.00%> (-1.16%)	⬇️

... and 359 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[dukenv0307]

@dukenv0307 clearPendingContactActionErrors is not used anywhere in the code base. Should I remove it?

Yes, we should do it

[dukenv0307]

Should fix it here?

It also happens on staging, right? And does it have the same RCA as the original issue?

I think the bug you mentioned is similar to the original one so we can raise the bounty if we fix it here.

[etCoderDysto]

It also happens on staging, right? And does it have the same RCA as the original issue?

Yes, it is also reproducible on staging.

I think the bug you mentioned is similar to the original one so we can raise the bounty if we fix it here.
Yes, we can do that. The issue is simialr but it has a different RCA

RCA:

We are passing addedLogin to validateCodeActionErrorField prop here

App/src/pages/settings/Profile/Contacts/NewContactMethodConfirmMagicCodePage.tsx

Line 55 in bceff96

validateCodeActionErrorField="addedLogin"

But Failed to send a magic code error is stored in actionVerified field of validateActionCode.errorFields. And when we click close button, we are trying to clear the error message from validateActionCode.errorFields.addedLogin field by calling clearValidateCodeActionError(validateCodeActionErrorField)

App/src/components/ValidateCodeActionModal/ValidateCodeForm/BaseValidateCodeForm.tsx

Lines 319 to 323 in bceff96

	onClose={() => {
	clearError();
	if (!isEmptyObject(validateCodeAction?.errorFields) && validateCodeActionErrorField) {
	clearValidateCodeActionError(validateCodeActionErrorField);
	}

Solution, we should clear the error from validateActionCode.errorFields.actionVerified field as well when Failed to send a magic code error is displayed

[dukenv0307]

@etCoderDysto make sense. Can you please update the PR with the solution above?

[etCoderDysto]

@etCoderDysto make sense. Can you please update the PR with the solution above?

Sure! I will do that.

[etCoderDysto]

@dukenv0307 I have made the change. Can you please review the code change? I have added a test for some of the pages that use BaseValidateCodeForm

[dukenv0307]

Reviewer Checklist

• I have verified the author checklist is complete (all boxes are checked off).
• I verified the correct issue is linked in the ### Fixed Issues section above
• I verified testing steps are clear and they cover the changes made in this PR
  • I verified the steps for local testing are in the Tests section
  • I verified the steps for Staging and/or Production testing are in the QA steps section
  • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
• I checked that screenshots or videos are included for tests on all platforms
• I included screenshots or videos for tests on all platforms
• I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
• I verified tests pass on all platforms & I tested again on:
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop
• If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
• I verified there are no new alerts related to the canBeMissing param for useOnyx
• I verified proper code patterns were followed (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
  • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I verified that this PR follows the guidelines as stated in the Review Guidelines
• I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
• If a new component is created I verified that:
  • A similar component doesn't exist in the codebase
  • All props are defined accurately and each prop has a /** comment above it */
  • The file is named correctly
  • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
  • The only data being stored in the state is data necessary for rendering and nothing else
  • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
  • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
  • All JSX used for rendering exists in the render method
  • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
• For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
• I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp

Screen.Recording.2025-10-30.at.11.09.19.mov

Android: mWeb Chrome

Screen.Recording.2025-10-30.at.11.07.15.mov

iOS: HybridApp

Screen.Recording.2025-10-30.at.11.10.18.mov

iOS: mWeb Safari

Screen.Recording.2025-10-30.at.11.06.21.mov

MacOS: Chrome / Safari

Screen.Recording.2025-10-30.at.11.00.10.mov

MacOS: Desktop

Screen.Recording.2025-10-30.at.11.11.00.mov

[OSBotify]

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

[OSBotify]

🚀 Deployed to staging by https://github.com/carlosmiceli in version: 9.2.41-0 🚀

platform	result
🖥 desktop 🖥	success ✅
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

[OSBotify]

🚀 Deployed to production by https://github.com/puneetlath in version: 9.2.41-6 🚀

platform	result
🖥 desktop 🖥	success ✅
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅