Are there any steps to make it work on your part?
I contacted the Partner Support with this issue.
On 28th of September they told me they were still looking into it and will get back to me once they find something…
They issue was still occurring for me when others in this thread already mentioned that it was fixed for them.
The partner support said that my deeplink looked perfectly fine (it was literally copied from the docs with the necessary changes).
I haven’t tried in a few weeks though so i might give it another try later today.
As of today, the issue still occurs for me.
The deeplink (id was removed):
window.open(
'https://' +
myshopifyDomain +
'/admin/themes/current/editor?template=product&addAppBlockId=app-id-from-env-file/better-bullets&target=newAppsSection',
'_blank',
)
With this being the folder structure of the extension:
And this being the schema of my app block:
Thank you for your input @Prudentt ![]()
I simplified my schema and used your deeplink structure. Unfortunately without success.
Have you confirmed that your extension id is correct? I had a similar issue where I was using the extension id from the incorrect environment (prod for stage, etc) when I was testing.
That was actually an idea I had.
In my .env file i can only see one SHOPIFY_THEME_APP_EXTENSION_ID and I think that is my production ID.
Could you tell me how I would find my Development ID?
Because I do use two different Apps, one for Production and one for Development.
Appreciate your help!
@mikefortney could you maybe elaborate on how you find the SHOPIFY_THEME_APP_EXTENSION_ID of a development build?
Never mind, I found the solution and posted above. Thanks for all the input guys.
Thank you and sorry for all the questions.
I tried that ID and it did not work. I just took another look at the documentation and there it says to use the SHOPIFY_EXTENSION_NAME_ID.
That constant is nowhere to be found in my project, even after running the deploy command. Does anyone have an idea where that could be found?
I finally got it to work!
To retrieve the correct uuid for the deeplink do the following (from this post ![]()
- Add your theme app extension to any store via the theme editor
- Go to the code editor of the theme’s code (right click → edit code)
- open the template file of the template to wich you added the App Block (for me it was the product page, so I had to open templates/product.json)
- look for the place where your app block is specified (see below for example)
- use the id at the end of the app blocks URL for your deeplink
Example (the relevant id is 00f4dfc0-0423-4d30-b597-21f3245b814e):
"28d695b7-72da-4c0e-973e-89e4a4d9658b": {
"type": "shopify:\/\/apps\/bloom-product-feature-bullets\/blocks\/better-bullets\/00f4dfc0-0423-4d30-b597-21f3245b814e",
"settings": {
"product": "{{product}}"
}
},
Well it turns out I just had a customer emailing me the same error message when trying to add my App to her Theme via Deeplink.
I am not able to replicate the Problem, not even when using the Theme she uses,
I will keep an eye on this.
It also occurs with our app. But it can not reproduce 100%, some shops work normally, some shops do not.
Just randomly occurred again yesterday (customer emailed me). And has been occurring here and there for some customers. So definitely not fixed yet.
@Liam can you please confirm whether this problem was ever fixed? This will help everyone in the above thread.
I had a customer contact me just yesterday about seeing this error… So it is definitely not fixed.
Hi…Is this fixed yet..Im seeing this with the judge app…only with the carroussel. I reinstalled the app and closed and opened Shopify. no change. thank you
This issue arose three times this week so far with customers. This is super annoying. @Liam are there any news regarding this from Shopify’s side?
I am experiencing this as well with Loox reviews app. @Liam is there any update please?
@Liam any updates?
I will remove deeplinks from my app for now and go back to a manual integration by the merchant.
I have had customers uninstalling my app naming as their reason that they don’t have time for this kind of troubleshooting. And I am 100% with them. This is just stupid.
Hi folks - no update as yet, but our team are still looking into this issue. Will post an update here asap.



