Wrong tax is displayed in checkout for Virtual products

[navarr]

Under certain scenarios the tax displayed in checkout for a virtual product does not match the address selected by the billing method

Preconditions

1. Magento 2.2.6-dev installed
   -- Updated(09/19/2019): Still actual on 2.3-develop
   -- Updated(02/15/2021): Modified for similar issue on 2.4-develop
2. Default Tax rates configured (typical of a clean installation)
3. Addition of a Tax Rule that enables those rates
   
4. A virtual product created with price point $10

Steps to reproduce

1. Create a customer account
2. Create a default billing & shipping address in New York, such as:
   123 Main St
   Flushing, NY 11354
3. Save
4. Browse to category to add Virtual product to cart
5. Proceed to checkout
6. Note sales tax of $0.84
7. Click "Edit" under the billing address
8. Click "Update"
9. Press back till you are no longer in checkout
10. Go to customer account page
11. Edit Address, set it to an address in California such as:
    1 Main St
    San Jose, CA 95131
12. Save
13. Click Mini-cart and click "Proceed to Checkout"

Video Recreation

Expected result

1. Sales tax of $0.83 (calculated off California address)

Actual result

1. Sales tax of $0.84 (calculated off New York address)

Notice

• Clicking a payment method in the checkout will show the California address as the selected address, despite showing the New York tax)
• After observing the results, if you go back to the cart and click "Update Cart" and then proceed to checkout, the correct sales tax will be displayed

[magento-engcom-team]

Hi @navarr. 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 (2.2-develop +).
For more details, please, review the Magento Contributor Assistant documentation.

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

• yes
• no

[navarr]

@magento-engcom-team give me 2.2-develop instance

[magento-engcom-team]

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

[magento-engcom-team]

Hi @navarr, here is your Magento instance.
Admin access: https://i-17425-2-2-develop.engcom.dev.magento.com/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[ghost]

@navarr , thank you for your report.
We've acknowledged the issue and added to our backlog.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!

[navarr]

@magento-engcom-team give me 2.4-develop instance

[magento-deployment-service]

Hi @navarr. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @navarr, here is your Magento Instance: https://5161c12f2cbe4c20a233551fe0791c52-2-4-develop.instances.magento-community.engineering
Admin access: https://5161c12f2cbe4c20a233551fe0791c52-2-4-develop.instances.magento-community.engineering/admin_d12c
Login: d101717e
Password: 823615cb0514

[navarr]

I've updated the issue with slightly different recreation steps for 2.4; as the original issue was fixed

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!

[navarr]

There hasn't been a non-patch release since the last time I confirmed this issue. I don't believe it's qualified to be stale yet

[Den4ik]

@magento I'm working on it