Setup Wizard Store details page, continue button is enabled even when email is null

[tapanshah21]

Prerequisites

• I have carried out troubleshooting steps and I believe I have found a bug.
• I have searched for similar bugs in both open and closed issues and cannot find a duplicate.

Describe the bug

On the Store details page of the WooCommerce setup wizard, the email field becomes mandatory if the newsletter signup checkbox is checked. However, in this particular scenario, we do not disable the Continue button and the user is able to click it. Clicking on the Continue button triggers two errors

1. There was a problem saving your store details
2. Invalid email address

Expected behavior

Like the rest of the fields, I would expect that if the newsletter signup checkbox is checked AND the email textbox is empty, we disable the Continue button in addition to triggering the validation message under the email textbox.

Actual behavior

When the newsletter signup checkbox is checked AND the email textbox is kept null or empty, the Continue button is enabled and I can click it. Clicking the Continue button triggers a 400 error.

Steps to reproduce

1. Go to the WooCommerce Setup Wizard >> Store details page (Step 1)
2. Fill in details like Address, Country, City, and Postcode
3. Check the Get tips, product updates and inspiration straight to your mailbox. checkbox
4. Ensure the email textbox is empty
5. Click on Continue
6. Observe the errors on the screen

WordPress Environment

https://lazy-cheetah.jurassic.ninja/wp-admin/admin.php

Isolating the problem

• I have deactivated other plugins and confirmed this bug occurs when only WooCommerce plugin is active.
• This bug happens with a default WordPress theme active, or Storefront.
• I can reproduce this bug consistently using the steps above.

[woocommercebot]

We are adding the status: needs reproduction label to this issue to try reproduce it on the current released version of WooCommerce.

Thank you for your patience.

[swatipawarGS]

Hi @tapanshah21 ,

Thank you for taking the time to report this bug, we really appreciate your help. We are able to reproduce the issue on our end using Woo Commerce 6.4.0 version and WordPress 5.9.3 version.

Please find below screencast/screenshots for reference :

Priority of this issue will be assigned shortly after we’d go through a round of prioritization. Please note it may take a couple of days.