Some checkout ui extension targets cannot be used in one-page checkout

[Tomoyuki_Kashiro]

Please list the package(s) involved in the issue, and include the version you are using

It’s not package related issue but checkout configuration editor (web ui).

Describe the bug

According to one-page checkout extension ui targets document, Delivery and Shipping metnod have following targets in one-page checkout.

• Delivery
  • purchase.checkout.delivery-address.render-before
  • purchase.checkout.delivery-address.render-after
• Shipping method
  • purchase.checkout.shipping-option-item.render-after
  • purchase.checkout.shipping-option-item.details.render
  • purchase.checkout.block.render [DELIVERY 1]

but in checkout configuration editor, I cannot see Delivery and Shipping method section to add app block when a store uses one-page checkout.

Steps to reproduce the behavior:

1. Create new dev store with checkout ui extensibility
2. Settings > Checkout > Click Customize in Configurations section
3. Click Settings in checkout editor then select one-page in Checkout layout section
4. Click Sections in checkout editor, you cannot see Delivery and Shipping method section to add app block

Expected behavior

We can set extension app to Delivery and Shipping method in one-page checkout as well as three-page checkout.

Notes

It’s a issue when a store uese one-page checkout, three-page checkout works as expected.

[Alex_Moser]

This seems to have happened recently. We have a public app that uses a checkout UI extension with the purchase.checkout.delivery-address.render-after target and we have never had an issue until I noticed I could not add the extension yesterday. This is a huge problem, obviously, as users are no longer able to install the extension for our app.

EDIT: Looks like this has been fixed!

[Tomoyuki_Kashiro]

Once I reported this issue, They fixed it

Thank you support team!