We have a checkout UI extension (at target purchase.checkout.block.render) on one of our merchant that renders a marketing consent checkbox. Its position is configured in the checkout editor to sit under the email field in the contact section.
This positioning works correctly on web, and in the mobile app (POQ App) for guest and already-signed-in flows. However, when a customer creates a new account during checkout in our mobile app (which loads checkout via the Checkout Kit for Web), the extension still renders — but gets pushed to the bottom of the screen instead of its configured position.
Our analysis: the block extension itself is intact and the extension content is present, so this appears to be the checkout editor’s configured position not being honoured specifically in the Checkout Kit for Web + new-account-creation path.
Here is a screen share that demonstrate a clear picture.