Can't create new customer account from frontend with required DOB field

[mrtuvn]

Preconditions (*)

1. 2.4-develop
2. php7.3
3. Default English locale

Steps to reproduce (*)

1. Enable DOB field from customer configuration (Show required)
2. Go to create new customer page

Expected result (*)

1. Form register customer should pass with valid dob

Actual result (*)

1. Form still show date of birth invalid and not allow to submit
   

[magento-deployment-service]

Thanks for opening this issue!

[m2-assistant]

Hi @mrtuvn. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

@mrtuvn do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[mrtuvn]

@magento give me 2.4-develop instance

[magento-engcom-team]

Hi @mrtuvn. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[magento-engcom-team]

Hi @mrtuvn, here is your Magento instance.
Admin access: https://i-26700-2-4-develop.instances.magento-community.engineering/admin_9e67
Login: 4dbca955 Password: 82415b898f5a
Instance will be terminated in up to 3 hours.

[magento-deployment-service]

Thanks for opening this issue!

[mrtuvn]

yes i have able to reproduced the issue on vanilla Magento instance following steps to reproduce

[magento-deployment-service]

Thanks for opening this issue!

[m2-assistant]

Hi @krishprakash. 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: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - 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.

[krishprakash]

@magento give me 2.4-develop instance

[magento-engcom-team]

Hi @krishprakash. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[magento-engcom-team]

Hi @krishprakash, here is your Magento instance.
Admin access: https://i-26700-2-4-develop.instances.magento-community.engineering/admin_5e87
Login: 66996247 Password: aeded9ca1339
Instance will be terminated in up to 3 hours.

[magento-engcom-team]

✅ Confirmed by @krishprakash
Thank you for verifying the issue. Based on the provided information internal tickets MC-31117 were created

Issue Available: @krishprakash, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[m2-assistant]

Hi @sudheers-kensium. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 2. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - 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!

• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[sudheers-kensium]

@magento give me 2.4-develop instance

[magento-engcom-team]

Hi @sudheers-kensium. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[magento-engcom-team]

Hi @sudheers-kensium, here is your Magento instance.
Admin access: https://i-26700-2-4-develop.instances.magento-community.engineering/admin_7579
Login: 2cba6bf0 Password: ba9a4fd2ed5b
Instance will be terminated in up to 3 hours.

[m2-assistant]

Hi @monikachintu. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 2. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - 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!

• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[magento-deployment-service]

Thanks for opening this issue!

[mrtuvn]

After workaround this i found problem seem related with dateformat + momenjs validate
Example in en_US locale
var test = moment("09/12/1911", "M/d/Y");
invalid

var test = moment("09/12/1911", "M/D/Y"); <= Work
valid

[www-vivek55]

@magento give me 2.4-develop instance

[magento-engcom-team]

Hi @vIvekSinGh55. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[magento-engcom-team]

Hi @vIvekSinGh55, here is your Magento instance.
Admin access: https://i-26700-2-4-develop.instances.magento-community.engineering/admin_78e8
Login: 52732e76 Password: 5792c4348ae6
Instance will be terminated in up to 3 hours.

[bubasuma]

Internal Magento team is working on this issue right now.

[magento-engcom-team]

Hi @mrtuvn, @monikachintu, @sertlab.

Thank you for your report and collaboration!

The issue was fixed by Magento team.

The fix will be available with the upcoming 2.4.0 release.

[azambon]

Fixed in 2.4, but this issue persists in 2.3

[hostep]

Looks like this is the commit which fixed it: MC-31117