Simplified Deployments - New version removes some extensions and now I can't add them back

Simplified Deployments - New version removes some extensions and now I can't add them back

gregmaxin
Shopify Partner
6 0 2

I switched over to simplified deployments and have around 9 extensions. When doing a test deployment, it didn't match 2 of the extensions to the existing extensions and instead, created two new extensions and removed the two current ones. (My thought is because we renamed them 6 months ago). For the other 6 extensions, it prompted me to match my local extensions to existing ones in Shopify

Before releasing the new version it shows a prompt saying these extensions will be removed. But my customers are using these extensions, and I need to find a way during `Shopify app deploy` to match the newly created extensions to the old extension IDs. Any help is much appreciated. 

 
 

8a11c67fb8bc37515034c8e0b9631b35 

 

 

 

Replies 4 (4)

akiladperera
Shopify Partner
2 0 0

This is a legit question for me as well. Desperately looking for a solution under the circumstance of not working the App embed block deep linking URL without renewing the extension. 

screen.JPGscreen1.JPG

gregmaxin
Shopify Partner
6 0 2

Hey.

I solved this issue by manually setting the extensionIDs in the `.env` file. The cli will read from this to automatically match extensions.

You can get the Ids for the existing extensions by looking at your version 0 (the first deployment after switching to simplified deployments) and manually going into each extensions and looking at the network request. Inside the request payload or response (can't remember) it will contain the Id. Copy this into your `.env` and then manually deploy from the cli to your production environment once and afterwards it should automatically match without issue. 

gregmaxin
Shopify Partner
6 0 2

It's a crude solution to a problem Shopify has not solved for me. Multiple tickets to them did not result in any solution

akiladperera
Shopify Partner
2 0 0

Thank you for the info. It really should have worked. Unfortunately, right now, they don't pull the extension id from .env file any longer. Lucky you.