Checkout. Quote Address Street cloning issue

[yutv]

Preconditions (*)

1. Magento 2.3.3 or 2.4-develop
2. Logged in Customer with an Address marked both as Shipping and as Billing.

Steps to reproduce (*)

1. Add a product to cart and go to the second step of checkout.

2. Open developer console and change billing address. e.g.

    require('Magento_Checkout/js/model/quote').billingAddress().street[0] = '123 Main Street'
   

Expected result (*)

1. Shipping Address remains the same

Actual result (*)

1. Shipping address street is changed to "123 Main Street"

Cloning Issue

The issue is here app/code/Magento/Checkout/view/frontend/web/js/action/select-billing-address.js#L21

and can be fixed by replacing:

address = $.extend({}, billingAddress);

to

address = $.extend(true, {}, billingAddress);

to clone address recursively including the street array.

[m2-assistant]

Hi @yutv. 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.

@yutv 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.

[m2-assistant]

Hi @sudheers-kensium. 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.

[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-26276-2-4-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[sudheers-kensium]

Hello @yutv , This is not an issue. It is working as expected because you marked both Shipping and as Billing address same.

I am closing this issue. Feel free to reopen if you feel that this is Magento core issue.

[yutv]

@sudheers-kensium

No, you are wrong. There is a bug. As you can see from the screenshot, changing the billing city doesn't lead to changing shipping city, but changing billing street does. An experienced front end developer may confirm that the issue exists.

[magento-engcom-team]

Hi @yutv. Thank you for your report.
The issue has been fixed in #26279 by @yutv in 2.4-develop branch
Related commit(s):

• 26872216194a2c534104573bb3e25075d933fc0c
• 4e81fd8452469c6497bd3362fe80d4006b43151b
• 974f5e934f14c4dff32717e0ebab4e1ae10bd1c0

The fix will be available with the upcoming 2.4.0 release.