If I’m developing an app, and my client-side code relies on sending/retrieving data through the shopify app proxy, why should the merchant be able to change this?
If a merchant changes the app proxy, my app breaks, right? Or am I using it the wrong way?
I’m just curious as to why it’s possible and what benefit this would bring to the merchant.
(The label doesn’t really suit this nor does the location - we really need labels and a section that’s more relevant to app development )
There’s a couple reasons why merchants might want to change the app proxy subpath or subpath prefix - such as customising the URL or to personalise it more closely with their branding. This is because the combination of the subpath prefix and subpath determines where the app proxy is accessed from a merchant’s shop, which is then reflected in their URL, so merchants may want to have more control over this.
You’re also correct that if a merchant changes the app proxy, it could potentially break your app if it’s not designed to handle such changes, and you’ll likely need to make a manual update to the theme or extension.
Any improvements for this scenario. I have been struggling quite a long time with this problem. The only workaround seems to prompt the merchant to add the proxy URL somewhere in my App so I can store/udate in an app metafield that can be read by my theme extension’s liquid.
Its a long path and not an ideal one to force the merchant to remember changing the proxy URL in the app config when it changes…
Any webhooks that fire when this config is changed? Any GrapQL API query/mutation to manage proxies?
Thanks for asking this Question. But it’s really important to know that Shopify has it’s own another platform for the Dev Community regarding the Shopify Shopify app Development Queries.
Here is the link: https://shopify.dev/
If you could post your Question there then you can get very fast and better solution.
Thanks