You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the store/shipping-options/{cart_id} endpoint in our Medusa store, the API returns an empty array instead of listing the available shipping options based on the cart's requirements. This issue does not occur when using the store/shipping-options endpoint, which correctly displays all shipping options with their respective minimum and maximum cart requirements. Additionally, attempting to manually add a shipping option that does not meet the cart requirements correctly prevents the addition, indicating some functionality of the shipping logic works as intended.
Steps to reproduce the behavior
Go to the Medusa store API endpoint store/shipping-options/{cart_id}.
Observe that the response is an empty array despite existing shipping options that should match the cart's criteria.
Compare with the results from the store/shipping-options endpoint where shipping options are displayed correctly.
Expected behavior
The expected behavior is that the store/shipping-options/{cart_id} endpoint should return a list of available shipping options that match the current cart's requirements, similar to how the generic store/shipping-options endpoint operates.
Screenshots
If applicable, add screenshots to help explain your problem.
The text was updated successfully, but these errors were encountered:
Bug report
Describe the bug
When using the
store/shipping-options/{cart_id}
endpoint in our Medusa store, the API returns an empty array instead of listing the available shipping options based on the cart's requirements. This issue does not occur when using thestore/shipping-options
endpoint, which correctly displays all shipping options with their respective minimum and maximum cart requirements. Additionally, attempting to manually add a shipping option that does not meet the cart requirements correctly prevents the addition, indicating some functionality of the shipping logic works as intended.Steps to reproduce the behavior
store/shipping-options/{cart_id}
.store/shipping-options
endpoint where shipping options are displayed correctly.Expected behavior
The expected behavior is that the
store/shipping-options/{cart_id}
endpoint should return a list of available shipping options that match the current cart's requirements, similar to how the genericstore/shipping-options
endpoint operates.Screenshots
If applicable, add screenshots to help explain your problem.
The text was updated successfully, but these errors were encountered: