I have a question regarding app proxy configuration and existing app users.
When I change the app proxy name, subpath, or other proxy details in my app’s shopify.app.toml file and run npm run deploy, Shopify CLI shows that the app proxy has been updated.
My question is:
If we update a Theme App Extension and deploy it, and the CLI also shows that the app proxy configuration has been updated, should the new proxy details automatically be updated for existing users under:
Or are there any additional commands or steps required to update the proxy details for existing app installations?
Currently, when I update the Theme App Extension and deploy it, the CLI recognizes the app proxy changes and shows them during deployment, but the proxy details do not appear to be updated for existing users.
Is this expected Shopify behavior? If so, what is the recommended way to update the app proxy configuration for existing users?
@Ajay_Rabari, I completely agree with you on this. I checked it from my side as well, and I’m seeing the same behavior.
Shopify mentions in their Shopify App Proxy documentation that url changes should apply immediately to existing stores, while prefix and subpath changes only apply to new installations.
However, in my testing, the updated proxy details didn’t reflect for existing installations either.
It would be great if Shopify provided a way to update proxy configuration for all existing installations, or offered a universal static proxy path for apps.
With most apps now relying heavily on App Blocks and storefront functionality, managing different proxy paths across existing and new stores can get messy pretty quickly.
@PRS03 Thank you for your response. Can we run multiple app proxies for one app?
Because in my live app code, I have changed the subpath and prefix and also changed them in the TOML file and pushed it via CLI. However, for existing users, the changes are not getting updated, so the app is getting broken on the storefront.
How should we handle this now? I need the new subpath and prefix, but the old users are still being affected by the changes.
Yes, this is quite strange from a developer point of view, as changing the proxy configuration through CLI doesn’t update it for existing users.
For now, the workaround is to keep the old proxy path working and redirect it from our app to the new proxy path. This way, old and new users both can be handled from one endpoint without breaking the storefront.
Currently, I think this is the practical way to handle it.
