Shipping address is not validated in checkout when proceeding step as logged in user with default shipping address

[DanieliMi]

Summary

The shipping address is not beeing validated (correctly?) for logged in users with addresses. If you already have customers in your shop and make changes to your address settings for your store this can lead to bad usability experience for your customers because they need to leave the checkout make change sin address book and then go back to checkout.

Preconditions (*)

1. v.2.2.6

Steps to reproduce (*)

1. Create a User
2. Go to My Account > Address Book
3. Add an default address (without a state)
4. In Admin Backend go to Stores > Configuration > General > State Options
5. Required State for a Country of your choice (I tested with Germany and United States)
6. With your created user put a product in your cart and proceed to checkout
7. Your created default address should be selected by default as shipping address
8. Proceed to step 2
9. Place Order

Expected result (*)

I expected to be stopped when trying to get to step 2 (Review & Payments) due to missing region in shipping address. I expected to get prompted to add the missing region.

Actual result (*)

It is possible to reach step 2 and press the Place Order button. Then I get the error message of the missing regionId.

[magento-engcom-team]

Hi @DanieliMi. 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-engcom-team give me $VERSION instance

where $VERSION is version tags (starting from 2.2.0+) or develop branches (for example: 2.3-develop).
For more details, please, review the Magento Contributor Assistant documentation.

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

• yes
• no

[DanieliMi]

I confirm i can reproduce the issue on vanilla Magento 2.2.6

[magento-engcom-team]

Hi @engcom-backlog-nazar. 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.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 6. Add label Issue: Confirmed once verification is complete.

• 7. Make sure that automatic system confirms that report has been added to the backlog.

[magento-engcom-team]

@engcom-backlog-nazar Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-96059, MAGETWO-96060 were created

[magento-engcom-team]

Hi @StasKozar. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if your 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.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

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

[magento-engcom-team]

Hi @DanieliMi. Thank you for your report.
The issue has been fixed in #19038 by @StasKozar in 2.3-develop branch
Related commit(s):

• 43e2c4dae51a62e169eed7ae6761f565d6780692
• b545997c49beec86291b4a28741c43d01c53c41e
• 66c1155ec7eb044df27435a5eb8bc20147359e72

The fix will be available with the upcoming 2.3.1 release.