Unable to publish Argo Extension

[Chong1]

Hi guys,

Is anyone facing the same problem with publishing the Argo subscription extension via the CLI? I am getting an error ` An error occurred while attempting to prepare your script` . I would kindly love any suggestions as to what might be caused this error?

I followed the steps here: https://shopify.dev/tutorials/getting-started-product-subscription-extension

1) shopify create extension --type=PRODUCT_SUBSCRIPTION --name="My test extension"
2) shopify register
3) shopify push

 Pushing your extension to Shopify ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
┃ Pushing code to Shopify...
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ (3.51s) ━━
X An error occurred while attempting to prepare your script.

I am using the default code provided by the Argo extension without any modifications to reduce the possibilities of my modified code being the root cause of the issue. 

Anyone have any experience with this? Thank you for your time.

[jlalande]

Hi @Chong1 , thanks for reaching out! 

Could you try to follow the `upgrading` steps here and see if the problem persists? https://shopify.dev/tutorials/getting-started-product-subscription-extension#upgradin

[Chong1]

Hey,

Thanks for the response. Yes, the `upgrade ` command seems to do the trick. I am able to publish the extension now.

[maxcoffer]

Hi @jlalande shouldn't package name there be "shopify-cli" instead of "shopify-run" at the "Upgrade the Shopify CLI" step here? https://shopify.dev/apps/subscriptions/app-extensions/getting-started#upgrading

brew upgrade shopify-run

[Chong1]

Hi jlande,

can you help us with the new argo extension bug that revolves around the inability to push the extension script to shopify after the command `shopify extension push`. The extension has been registered with an app and once again, I am using the default code to eliminate any possibilities of my code being the root cause of the issue.

The tutorial that you've linked earlier had undergone some updates and the solution no longer works. I've attached a screenshot of the bug below. 

Thank you for your time 🙂