Checkout UI Extension not rendering for subset of merchants - fixed by any checkout editor save

Extensions
1

Hi,

We’re seeing a sporadic but reproducible issue affecting a subset of our merchants since Monday (Feb 23), and we’d love some help understanding the root cause.

The symptom:

Our checkout UI extension is present and correctly positioned in the checkout editor, but is simply not rendering on the live checkout. No errors visible to the shopper - the extension block just doesn’t appear.

The fix (workaround):

Making any change in the checkout editor and saving resolves it immediately for that merchant - the extension reappears on the next checkout load. The change doesn’t need to be related to our extension (e.g. moving an unrelated block, changing a colour setting, then saving is enough).

Extension details:

  • Type: ui_extension

  • API version: 2025-07

  • Framework: React (@shopify/ui-extensions-react v2025.7)

  • Capabilities: api_access, network_access, block_progress

  • Targets: purchase.checkout.block.render, purchase.checkout.shipping-option-list.render-before, purchase.checkout.shipping-option-list.render-after, purchase.checkout.pickup-location-list.render-after

What changed on Monday:

The only app change we deployed on Monday was adding a new scope to our shopify.app.toml and running shopify app deploy. Merchants were prompted to approve the new scope in the Shopify Admin, which they did. No changes were made to the extension code or TOML itself - the extension bundle is identical.

What we’ve ruled out:

  • The extension is not being returned null prematurely - our extension has several early-return guards (e.g. checkout_disabled metafield flag, isFulfillmentActive, country zone matching), but the workaround of re-saving the checkout editor bypasses all of these without any configuration change, which suggests this is a platform-level state issue rather than our code

  • It’s not 100% correlated to the scope approval - some merchants who approved the scope are unaffected, and the timing of the approval doesn’t appear to predict which merchants are impacted

  • The extension is correctly listed as active in the checkout editor for all affected merchants

Our hypothesis:

The shopify app deploy with a new scope may have created a new app version that put some merchants’ checkout profiles into a stale or “draft” state - where the checkout editor still shows the extension as active, but the published checkout profile doesn’t include it. Saving anything in the checkout editor forces a re-publish of the profile, which resolves it.

Questions:

  1. Is it known that running shopify app deploy (to update scopes) can invalidate or draft-ify published checkout extensions for a subset of merchants?

  2. Are there any known current issues with checkout UI extensions?

  3. Is the cause due to our extension not using latest API versions?

Any help greatly appreciated - this is production-impacting for merchants and we want to understand if this is a known platform behaviour.

Thanks

2

Hi @Alex_Hooper

I’m digging into the expected behaviour for how published extensions should react following a new deploy, but in the meantime something you could try is to use the Admin GraphQL API to query the checkoutProfiles for affected vs. unaffected merchants and compare the updatedAt and editedAt timestamps. This can confirm whether the profiles of affected merchants were not re-published after your deploy:

query {
  checkoutProfiles(first: 5) {
    nodes {
      id
      name
      isPublished
      createdAt
      editedAt
      updatedAt
    }
  }
}

This would let you check whether there’s a correlation between the timing of the merchant’s scope approval and the updatedAt of their published checkout profile. If the profile’s updatedAt predates the deploy, that strongly supports your theory.

I don’t think this is related to an outdated API version - but it’s worth upgrading to the latest version as a general best practice.

1 Like
4

@Alex_Hooper, can you let me know if you’re still experiencing this issue or if it has been resolved?