Require Emails Confirmation behavior issue

[coresh]

Preconditions and environment

• Magento version: v2.4.7
• Pwa Studio v14.0.0

Steps to reproduce

1. Config. core_config_data: customer/create_account/confirm is 1
2. Guest
3. Add any product to cart.
4. Go to https://example.com/checkout
5. Click to "Sign In" button
6. Click to "Create An Account" button
7. Submit form data

Expected result

The notification:

"Please check your email for confirmation key."

Actual result

The notification:

"An error has occurred. Please check the input and try again."

Additional information

Admin -> Stores -> Configuration -> Customer Configuration -> Create New Account Options

Path:
https://www.example.com/checkout

Form submission result:

Backend log output:

./var/log/exception.log <==
[2024-05-14T11:30:49.798471+00:00] report.ERROR: The account sign-in was incorrect or your account is disabled temporarily. Please wait and try again later.

GraphQL (2:3)
1: mutation SignInAfterCreate($email: String!, $password: String!) {
2:   generateCustomerToken(email: $email, password: $password) {
     ^
3:     token
 {"exception":"[object] (GraphQL\\Error\\Error(code: 0): The account sign-in was incorrect or your account is disabled temporarily. Please wait and try again later. at vendor/webonyx/graphql-php/src/Error/Error.php:155)
[previous exception] [object] (Magento\\Framework\\GraphQl\\Exception\\GraphQlAuthenticationException(code: 0): The account sign-in was incorrect or your account is disabled temporarily. Please wait and try again later. at vendor/magento/module-customer-graph-ql/Model/Resolver/GenerateCustomerToken.php:59)
[previous exception] [object] (Magento\\Framework\\Exception\\AuthenticationException(code: 0): The account sign-in was incorrect or your account is disabled temporarily. Please wait and try again later. at vendor/magento/module-integration/Model/CustomerTokenService.php:107)"} []
[2024-05-14T11:30:49.798471+00:00] report.ERROR: The account sign-in was incorrect or your account is disabled temporarily. Please wait and try again later.

Thank you

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• 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]

Hi @coresh. 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. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• 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.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 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]

Hi @engcom-Dash. 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).
• 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

     - 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!

---

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

[coresh]

The issue moved to: magento/pwa-studio#4265