Internal Server Error in /V1/order/{orderId}/ship API Endpoint

[mlf20]

Preconditions and environment

• Magento version 2.4

Steps to reproduce

1. Retrieve auth token from the admin endpoint /V1/integration/admin/
2. Request endpoint: POST : //yourstore/rest/V1/order/{orderId}/ship Payload: { "items": "[]" }

Other below APi's also got effected and getting similar error in logs:

1. POST request to /V1/inventory/stock-source-links with payload: {"links": "[]"}
2. POST request to /rest/V1/inventory/source-items with payload: {"sourceItems": "\[]\"}
3. POST request to //V1/inventory/low-quantity-notification with payload: {"sourceItemConfigurations": ""}
4. POST request to /rest/V1/inventory/stock-source-links-delete with payload: {"links": "\[]\"}

Expected result

Returns a 400 error as the request is malformed.

Actual result

Returns a 500 status code from a null TypeError .

Additional information

output of var/log/system.log:

    [2022-08-01T12:54:49.463557+00:00] main.CRITICAL: TypeError: Magento\Sales\Model\ShipOrder::execute(): Argument #2 ($items) must be of type array, null given in /magento/vendor/magento/module-sales/Model/ShipOrder.php:133
    Stack trace:
    #0 [internal function]: Magento\Sales\Model\ShipOrder->execute()
    #1 /magento/vendor/magento/module-webapi/Controller/Rest/SynchronousRequestProcessor.php(95): call_user_func_array()
    #2 /magento/vendor/magento/module-webapi/Controller/Rest.php(188): Magento\Webapi\Controller\Rest\SynchronousRequestProcessor->process()
    #3 /magento/vendor/magento/framework/Interception/Interceptor.php(58): Magento\Webapi\Controller\Rest->dispatch()
    #4 /magento/vendor/magento/framework/Interception/Interceptor.php(138): Magento\Webapi\Controller\Rest\Interceptor->___callParent()
    #5 /magento/vendor/magento/framework/Interception/Interceptor.php(153): Magento\Webapi\Controller\Rest\Interceptor->Magento\Framework\Interception\{closure}()
    #6 /magento/generated/code/Magento/Webapi/Controller/Rest/Interceptor.php(23): Magento\Webapi\Controller\Rest\Interceptor->___callPlugins()
    #7 /magento/vendor/magento/framework/App/Http.php(116): Magento\Webapi\Controller\Rest\Interceptor->dispatch()
    #8 /magento/generated/code/Magento/Framework/App/Http/Interceptor.php(23): Magento\Framework\App\Http->launch()
    #9 /magento/vendor/magento/framework/App/Bootstrap.php(264): Magento\Framework\App\Http\Interceptor->launch()
    #10 /magento/pub/index.php(30): Magento\Framework\App\Bootstrap->run()
    #11 {main} [] []

Release note

No response

Triage and priority

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [ ] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• [X] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• [ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant[bot]]

Hi @mlf20. Thank you for your report. To speed up processing of this issue, make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, review the Magento Contributor Assistant documentation.

Add a comment to assign the issue: @magento I am working on this

To learn more about issue processing workflow, refer to the Code Contributions.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

  :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

:clock10: You can find the schedule on the Magento Community Calendar page.

:telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant[bot]]

Hi @engcom-November. 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: :point_down:

• [ ] 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.

[engcom-November]

Hi @mlf20 , Thank you for reporting and collaboration. This issue is not reproducible on 2.4-develop branch The exception mentioned in all the below issues reported by you is the similar error/ issue which is not reproducible on 2.4-develop branch. Can we close all the other issues and track in a single bug: https://github.com/magento/magento2/issues/35934 Similar issues having same kind of exception: https://github.com/magento/magento2/issues/35929 https://github.com/magento/magento2/issues/35928 https://github.com/magento/magento2/issues/35927 https://github.com/magento/magento2/issues/35926 https://github.com/magento/magento2/issues/35931 https://github.com/magento/magento2/issues/35930

We are getting a 400 error as the request is malformed. Kindly check Magento system requirements and 3rd party exntensions / modules enabled is causing this issue. Kindly recheck the issue on Magento 2.4-develop branch and provide missing steps if any if you are still facing any issues. Thank you

[mlf20]

Hi @engcom-November

I have gone over my logs and the payload in the body should be '{}'

This reproduces the issue on Magento 2.4-dev as shown below:

[engcom-November]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @engcom-November. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @engcom-November, here is your Magento Instance: https://64d98f06e55e370be8728bd1aee78bb0.instances.magento-community.engineering Admin access: https://64d98f06e55e370be8728bd1aee78bb0.instances.magento-community.engineering/admin_0ae1 Login: 55ee1fc2 Password: 149b20bb8020

[engcom-November]

Verified the issue on Magento 2.4-develop branch and the issue is reproducible. Hence updating the description and confirming the issue

[github-jira-sync-bot]

:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-6420 is successfully created for this GitHub issue.

[m2-assistant[bot]]

:white_check_mark: Confirmed by @AmyJZhao. Thank you for verifying the issue.
Issue Available: @AmyJZhao, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[Alexander-Khohklov]

@magento I am working on this

[Monica8955]

any news of this request? i have the same issue for magento 2.4.6-p2