Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Shipping address is not set" exception in Multishipping Checkout. #16555

Closed
p-bystritsky opened this issue Jul 5, 2018 · 7 comments
Closed
Assignees
Labels
Component: Multishipping Fixed in 2.1.x The issue has been fixed in 2.1 release line Fixed in 2.2.x The issue has been fixed in 2.2 release line Fixed in 2.3.x The issue has been fixed in 2.3 release line Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Progress: PR Created Indicates that Pull Request has been created to fix issue Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release

Comments

@p-bystritsky
Copy link
Contributor

Preconditions

  1. Magento 2.
  2. Multishipping Checkout enabled (by default)
  3. Simple Product.
  4. Customer.

Steps to reproduce

  1. Log In as Customer.
  2. Add Product to Cart.
  3. Proceed to Checkout.
  4. Fill Shipping Address data, click Next (do not place Order)
  5. Return to the Storefront.
  6. Go to the Shopping Cart.
  7. Click Check Out with Multiple Addresses.

Expected result

  1. Correct Multishipping Checkout workflow.

Actual result

  1. Exception #0 (Magento\Framework\Exception\StateException): Shipping address is not set
  2. Exception #0 (Zend_Db_Statement_Exception): SQLSTATE[23000]: Integrity constraint violation when trying to access Shopping Cart.
@magento-engcom-team
Copy link
Contributor

Hi @p-bystritsky. 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.

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

  • yes
  • no

@magento-engcom-team magento-engcom-team added the Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed label Jul 5, 2018
@ghost ghost self-assigned this Jul 5, 2018
@ghost ghost added Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release labels Jul 5, 2018
@ghost
Copy link

ghost commented Jul 5, 2018

We've acknowledged the issue and added to our backlog.

@dmytro-ch
Copy link
Contributor

I will handle this issue.

@dmytro-ch dmytro-ch self-assigned this Jul 12, 2018
@ghost ghost removed their assignment Jul 12, 2018
dmytro-ch added a commit to dmytro-ch/magento2 that referenced this issue Jul 13, 2018
@ishakhsuvarov ishakhsuvarov added the Progress: PR Created Indicates that Pull Request has been created to fix issue label Jul 27, 2018
dmytro-ch added a commit to dmytro-ch/magento2 that referenced this issue Aug 4, 2018
dmytro-ch added a commit to dmytro-ch/magento2 that referenced this issue Aug 4, 2018
dmytro-ch added a commit to dmytro-ch/magento2 that referenced this issue Aug 4, 2018
@rogyar
Copy link
Contributor

rogyar commented Aug 8, 2018

I'm able to reproduce this issue on the 2.2-develop branch.

@magento-engcom-team
Copy link
Contributor

Hi @p-bystritsky. Thank you for your report.
The issue has been fixed in #16753 by @dmytro-ch in 2.2-develop branch
Related commit(s):

The fix will be available with the upcoming 2.2.7 release.

@magento-engcom-team magento-engcom-team added the Fixed in 2.2.x The issue has been fixed in 2.2 release line label Aug 9, 2018
@sidolov
Copy link
Contributor

sidolov commented Aug 14, 2018

Hi @p-bystritsky. Thank you for your report.
The issue has been fixed in #16783 by @dmytro-ch in 2.1-develop branch
Related commit(s):

The fix will be available with the upcoming 2.1.16 release.

@sidolov sidolov added the Fixed in 2.1.x The issue has been fixed in 2.1 release line label Aug 14, 2018
@magento-engcom-team
Copy link
Contributor

Hi @p-bystritsky. Thank you for your report.
The issue has been fixed in #16784 by @dmytro-ch in 2.3-develop branch
Related commit(s):

The fix will be available with the upcoming 2.3.0 release.

@magento-engcom-team magento-engcom-team added the Fixed in 2.3.x The issue has been fixed in 2.3 release line label Aug 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Multishipping Fixed in 2.1.x The issue has been fixed in 2.1 release line Fixed in 2.2.x The issue has been fixed in 2.2 release line Fixed in 2.3.x The issue has been fixed in 2.3 release line Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Progress: PR Created Indicates that Pull Request has been created to fix issue Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release
Projects
None yet
Development

No branches or pull requests

6 participants