App proxy URL changed storefronts still using old proxy path; how to update or detect per-store proxy?

I changed my app proxy URL (updated shopify.app.toml / Partner Dashboard) the new proxy works for new installs, but existing stores keep using the old proxy path (or some merchants may have manually edited the proxy path). I need a reliable way to (a) fetch the correct proxy path from storefront code or (b) update/force the proxy path for already-installed shops. Looking for best practices and pitfalls to avoid.

What I see (actual behavior)

  • New installs use the new proxy path (e.g. /apps/my-new-handle)
  • Old stores still respond on the old proxy path (e.g. /apps/my-old-handle)
  • I can’t find an Admin API that reliably returns the per-store proxy path

What I tried

  1. Updated shopify.app.toml and deployed the app. New installs are fine.
  2. Checked docs/community — looks like Partner Dashboard/app config should propagate the proxy path to existing installs, but merchants can edit the path per-store in admin which breaks hardcoded storefront links.
  3. Considered reinstalling the app on affected stores (works but not scalable).

Thanks in advance any pointers, official docs I missed, or tooling snippets would be really helpful.

1 Like

Hey @Vipul_Pandey, this is a known limitation (related thread here).

This is still something our team is looking in to improving.

1 Like

Thanks @KyleG-Shopify looking forward to a solution. I’ll follow the thread you shared for updates.

Hello @KyleG-Shopify ,

Is there already a solution available? I believe this is quite a significant issue.

Hey @online_origins , no new updates to share at this point. I would suggest following this thread here as that’s where we will update if there is a change.

Also keep an eye on the developers changelog.

Hi. @Vipul_Pandey , what did u change? The url or subpath that doesn’t change for old users?

It’s also very important to me because I’ll use another url in the feature to direct api to a dedicated server.