2.2 - Admin will not create shipment from the invoice create screen if credit card was used

[mzenner1]

I'm using Magento 2.2.3 and seeing an issue where if an order was made with a credit card (authorize.net), when I go to the admin to create an invoice and check the "Create Shipment" box it will have a success message, create the invoice properly, but no shipment will be created.

This only happens if a credit card is used. If I make another order using Purchase Order as the payment type, the shipment will be created successfully via the invoice creation screen.

Precondition

Magento 2.2.x or 2.3.x

Steps to reproduce

1. Enable authorize.net
2. Purchase a product with a credit card
3. Go to the admin->sales->orders section
4. Invoice the order
5. Check the "Create Shipment" button
6. Submit the invoice

Expected result

1. Both an invoice AND a shipment should have been created

Actual result

1. Only an invoice gets created, the shipment does not

I am seeing this error in the exception log at the time of invoice creation

[2018-03-08 13:55:30] main.CRITICAL: Unable to get transaction details. Try again later. {"exception":"[object] (Magento\Framework\Exception\LocalizedException(code: 0): Unable to get transaction details. Try again later. at /vendor/magento/module-authorizenet/Model/TransactionService.php:135)"} []

[magento-engcom-team]

@mzenner1 , thank you for your report.
We were not able to reproduce this issue by following the steps you provided. Please provide more detailed steps to reproduce or try to reproduce this issue on a clean installation or latest release.

[mzenner1]

I am able to replicate this on a blank 2.2.3 install. I see the success message in your screenshot above. I too am getting that same success message (that both items were created). However, if you actually go to Sales->Shipments, was that shipment really created? For me it is not.

[magento-engcom-team]

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

[m2-assistant]

Hi @engcom-Charlie. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 2. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

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