Open WoodlegDev opened 4 months ago
issue still exists
@WoodlegDev Is this issue resolved? If yes, how??
@scriptorShiva unfortunately not. We implemented for the time custom logic, but it's not optimal. It's not critical for us anymore - but in my experience help is better on the discord
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.
![image](https://github.com/medusajs/medusa/assets/67638254/0aa8de15-1f66-471f-b57e-fe1eb0199f2c)