Telephone field in customer account does not validate

[marctbb]

Preconditions and environment

Magento 2 versions tested:

• 2.4.6-p4 (with the default Blank theme).
• 2.4.7 (also tested with the default Blank theme).

Configuration:

• Stores > Configuration > Customers > Customer Configuration > Show Telephone: Set to Required.

Issue observed in both environments and themes.

Steps to reproduce

1. Go to My Account as a logged-in customer.
2. Attempt to Add or Edit the telephone field under account details.
3. Enter invalid input, such as text or symbols (e.g., "abc123" or "!@#").
4. Save the changes.

Expected result

• The telephone field in the My Account section should validate input to ensure it is a valid phone number (e.g., digits only, proper phone format).
• Invalid input should trigger an error message and prevent saving.

Actual result

• The telephone field in My Account allows invalid input (e.g., text or symbols) without validation.
• In the checkout, when retrieving customer details from the account, the invalid phone number causes errors during the shipping process.
• For example, UPS shipping fails to process the order due to incorrect phone number format.

Additional information

• Video evidence of the issue is attached for reference.
• The issue occurs regardless of the Magento version (tested on 2.4.6-p4 and 2.4.7) or theme used (Blank theme).
• This inconsistency between the My Account section and Checkout makes it critical, as incorrect phone numbers lead to shipping failures.

https://github.com/user-attachments/assets/10689ac7-e900-4111-a35a-e1bde0c7e217

Release note

No response

Triage and priority

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [X] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• [ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant[bot]]

Hi @marctbb. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this

• To learn more about issue processing workflow, refer to the Code Contributions.

  Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant[bot]]

Hi @engcom-Delta. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• [ ] 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• [ ] 5. Add label Issue: Confirmed once verification is complete.
• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Delta]

Hi @marctbb ,

Thanks for your reporting and collaboration. We have verified the issue in Latest 2.4 develop instance, but we are unable to reproduce the issue. Kindly refer the screenshots.

Steps to reproduce Stores > Configuration > Customers > Customer Configuration > Show Telephone: Set to Required.

1. Go to My Account as a logged-in customer.
2. Attempt to Add or Edit the telephone field under account details.
3. Enter invalid input, such as text or symbols (e.g., "abc123" or "!@#").
4. Save the changes. Observe Error displays when user fill invalid phone number

Can you please re-verify and confirm if you are still facing the issue. Thanks.