Releasing a new version from the Dev Dashboard breaks the extension when using a custom version name

Shopify App Store
1

Hi,

I released a new version of the app from the Dev Dashboard using Release button. The only changes in this release were updating the auth URL and the app URL.

During the release, it asked for a version name. Instead of leaving it empty, I entered “updated”.

Right after deploying, the theme extension broke on all stores. All extension assets started returning 404 errors.

Here are sample asset URLs for reference:

https://cdn.shopify.com/extensions/019d5162-bde7-7069-aac3-0827dd6db72c/{versionName}/assets/core.bundle.js

After this release, the URL became:

https://cdn.shopify.com/extensions/019d5162-bde7-7069-aac3-0827dd6db72c/updated/assets/core.bundle.js

This above sample URLs with version name “updated” were returning 404.

No other changes were made in the code or extension, only the auth url (which shouldn’t affect the extension) and the version name during release.

This looks like the issue is caused by using a custom version name during new version release.

SCR-20260403-iwsh
SCR-20260403-iwsh1434×561 48 KB

2

Hey again @Gulam_Hussain - thanks for flagging this, and for the detailed repro steps + screenshot. This does look a bit weird to me. It seems like the custom version name you entered during the release is being used directly in the CDN asset path, which would explain the 404s if the assets weren’t actually published under that path.

Just to confirm a couple things so I can dig into this on our end:

  • Was the extension working as expected on the previous version before this release?
  • Have you tried releasing another version since (with the version name left empty) to see if that resolves the 404s?

Happy to look into this further on our end here, thanks again for flagging. Hope to hear from you soon!

3

Hi, yes the extension was working completely fine before this.

After I manually released a version with a custom name, the 404 errors started happening. I didn’t notice it immediately, my customers actually reported that the app stopped working, which is when I checked and found the issue.

I then tried releasing another version from the dashboard UI, this time using a version name similar to the previous ones and just incrementing it, but that didn’t fix it, the 404s were still there.

After that, I released a new version using the CLI and that finally fixed everything, assets started loading properly again.

To test, I just released another version from the dashboard UI and left the version name empty. Shopify generated a version name automatically, but it didn’t match the pattern of my earlier versions, and I started getting the same 404 errors. So now i have reverted back to CLI released version

So it looks like releases from the dashboard UI are consistently causing this issue

4

@Alan_G I just released a new version of a completely different app from another partner account and left the version name empty, and I’m seeing the same 404 error there as well.

5

Thanks for confirming @Gulam_Hussain - I’ll flag this and we’ll take a look on our end. I’ll loop back with you here once I have more info.