Why doesn't my app's embed toggle show up in Theme Settings until the developer redeploys?

If a newly installed app's on/off switch won't appear under App embeds no matter how many times you refresh the theme editor, the extension almost certainly hasn't been deployed and released yet.

app-embedstheme-editortheme-app-extensionsdeployment

What's going on

A merchant installs an app that's supposed to add something visible on the storefront, a chat widget, an announcement bar, a cart drawer upsell, tracking pixels bundled as a theme app extension, and goes looking for the on/off switch. In the theme editor, that switch lives under Theme Settings, App embeds, a list of every app embed block available to the current theme, each with its own toggle. The problem is that the app just installed simply isn't in that list. No error, no broken link, just an empty spot where the toggle should be.

Then, sometimes hours later, or after the developer pushes another change, the toggle appears and works fine. That timing makes it look like the toggle is somehow tied to a redeploy, which is confusing when you did nothing between the first failed check and the later successful one except wait, or when you assume the app is simply broken and reinstall it, wasting time and occasionally creating a duplicate app record in the process.

This is a real and fairly common gap, but it isn't a bug in the toggle itself. It's a gap in the app's own build and release sequence, or in the store's theme setup, that has nothing to do with anything the merchant did.

Why it happens

App embeds and app blocks come from a theme app extension, a separate artifact from the app's main install flow. Installing the app grants it access to your store; it doesn't automatically make its theme app extension available in the theme editor. For the embed to show up under App embeds, the developer has to build the extension, deploy it, and then release that version so it becomes the app's active version. If any of those steps is skipped, delayed, or fails silently, which happens fairly often on the developer's end, the embed block genuinely does not exist yet from the theme's point of view, and no amount of refreshing on your side will surface it.

A second, less obvious cause is that even after a valid deploy, the theme editor can take a little time to pick up a newly released extension version, and the active theme needs to support app embeds (the newer Online Store theme architecture) for the list to populate correctly. If you're editing the wrong theme, or an older incompatible one, the toggle won't appear no matter what the developer has done.

Because the deploy and release step happens entirely on the app's side, it looks random and tied to redeploys from where the merchant sits, even though from the developer's side it's a predictable consequence of an incomplete or delayed release.

5 ways to fix it

1

Ask the app's support team to confirm the extension is deployed and released

This resolves it in almost every case and costs you nothing. Tell the app's support contact exactly what you're seeing, that the embed toggle isn't showing under Theme Settings, App embeds, and ask them to confirm their theme app extension has been deployed and released to your store. A responsive app team can check this from their own dashboard in minutes. If the extension was never released, that's the actual root cause, not anything wrong with your theme or store.

2

Check that you're editing the right, currently published theme

In Online Store, Themes, confirm you're customizing the theme that's actually live, or the correct duplicate if you're testing on one. App embeds only populate for the theme you have open in the editor, and it's easy to lose track of which draft or duplicate is active when a store keeps several around. If you were editing a stale duplicate, switching to the live theme and reopening App embeds often resolves it immediately.

3

Wait and do a hard refresh rather than reinstalling the app

If the developer confirms the extension is deployed and released, give the theme editor a little time and do a full refresh, not just re-opening the same tab, before assuming something is broken. Uninstalling and reinstalling doesn't speed this up, and it can leave duplicate app records or orphaned settings behind once the extension does register, so treat reinstalling as a last resort, not a first troubleshooting step.

4

Ask if the app offers a direct link into the App embeds panel

Some apps provide a link that opens the theme editor with their embed toggle already in view, so you can enable it without hunting through the full list. If the app's onboarding instructions or admin screen mentions one, it's a convenient shortcut, but it still depends on the extension being deployed first, it gets you to the toggle faster, it doesn't create the toggle.

5

If you're the developer, build the deploy-and-release step into your install flow

The durable fix belongs upstream. Automate your extension deploy and release as part of your build pipeline so it's live before or immediately after a merchant finishes installing, and give your support team a way to check a store's release status instead of guessing. This is a process and tooling gap, so if you don't have that expertise in house, an agency partner who handles Shopify app deployment and release automation is a better fit than trying to patch it after the fact.

Bottom line

In nearly every reported case, this comes down to a theme app extension that hasn't finished its deploy and release cycle, not a setting you're missing or a Shopify outage. As a merchant, the fastest path is asking the app's support team to confirm the extension was released and double-checking you're on the correct theme. If you're the developer on the other side of this, the lasting fix is tightening your own deploy pipeline, or getting help from a Shopify agency on release automation, rather than leaving merchants to wait it out.

Still Stuck?

Browse the rest of the problem library, run a free storefront scan to catch issues like this automatically, or email us and we'll work out a custom solution for it.