I have created app from https://partners.shopify.com and use Admin Link to create new link Link target URL ( https://www.example.com/shopify/extension/products ) and Page to show link( Product Details ) but after successful installation it's show's modified link https://mydemo-store.myshopify.com/admin/apps/mydemo/shopify/extension/products?id=393110552725&shop=mydemo-store.myshopify.com .
1. Create new app from https://partners.shopify.com
2. Click on Extensions and add new link from Admin Links ( Link target URL )
3. After install you will see link is modified on More Actions
Let me know if I missed anything
Please produce more details. Your question as it stands seems to make no sense to me. You state the following.
- created a target URL of /shopify/extension/products (forget your FQDN, an embedded App will not show that, but will use that)
- Shopify sends the product ID and shop name to /shopify/extensions/products as it should. (note the FQDN is simple hidden as in any embedded App)
So what is the problem? This is exactly how the link should be, and if you tested it out, your App at https://www.example.com/shopify/extensions/products would be hit. Are you saying that is not the case? If so, are you sure your App is working correctly?
I think the issue is the lack of concise documentation around app extensions.
THere are many ways that an 'embedded' app or an app extension could be imagined and without proper explanation, it's not obvious exactly how SHopify chose to implement them.
After experimentation, it appears that an iframe is used to 'surface' my external resource within shopify. So when we create 'target links' for an app extension, it's not creating a direct link to an external resource. It's loading our internal admin url for our app, followed by the 'path' portion of the remote target link url we set in the Admin link to make a unique URL for this. Then, an iFrame is rendered into the page which grabs the content from our full, original remote URL .
I'm not questioning Shopify's reasons for building things in this way, though I do think it's odd. I"m sure they have good reasons at this point. But I am suggesting that they need a better, deeper, and fuller set of documents explaining the system for developers.
It is true, that this particular resource is UNDER serviced by Shopify. If you examine the Shopify open source App code for embedded Apps, you can see how there is zero support for App links using the new JWT token authentication scheme. That means you're getting hit in your App without a chance to authenticate with JWT. Which is totally understandable, how could Shopify know if your App extension is authenticated or not! But then, what is the point of moving everyone to JWT if this this fundamental exercise does not fit?