Can any Shopify staff tell us why extensions are failing dev preview?

Shopify CLI and Libraries
1

We’re migrating extensions from React to Preact, and suddenly it just stops building the dev preview. If we replay our branch from 2 days ago, 5 days ago, 10 days ago versions of our app code that would run locally a week ago won’t enter dev preview.

Can anyone working at Shopify tell us why these requests fail to start a preview?

Request ID: da4e4dcb-8cf4-400c-9978-ddcadc435bd1-1780758132
Request ID: 8f59e22b-f016-48c3-b4bb-fce1b6fbd7f2-1780757555
Request ID: 3af8d6cd-6957-4467-bcc7-ecde42ddc191-1780757218

2

Request ID: 876a08d9-799e-41e3-a514-0da5f56d90a8-1780846153

I know that there are some undocumented ways a Shopify extension could fail dev preview looking at other posts if there are more than (3) extensions per target, but after printing the targets used, I am at (3) or below for each target.

extensions/_tests/customerAccountTargetRegistrationLimit.test.ts:
Customer Account target registrations:
 3 customer-account.order-status.block.render (ca-offers-grid, customers-accounts, thank-you-featured)
 1 customer-account.order-status.cart-line-item.render-after (ca-cart-line-item-switch-products)
 1 customer-account.order-status.cart-line-list.render-after (ca-orders-apply-post-purchase-code)
 1 customer-account.order-status.customer-information.render-after (ca-shipping-address)
 3 customer-account.order-status.fulfillment-details.render-after (ca-orders-edit-shipping-address, ca-orders-edit-shipping-method, order-status-static)
 3 customer-account.order-status.payment-details.render-after (ca-free-shipping-threshold, ca-orders-inline-download-invoice, ca-shipping-rates)
 2 customer-account.order.action.menu-item.render (ca-cancel-order, ca-orders-print-invoice)
 2 customer-account.order.action.render (ca-cancel-order, ca-orders-print-invoice)
 1 customer-account.page.render (ca-continue-shopping)
✓ Customer Account extension target registration limits > keeps active customer-account target registrations at or below Shopify's limit [16.01ms]
4

@keiraarts, I had a look at our logs for those Request IDs, and they’re showing a file upload timeout. Since your extensions previewed fine a week ago, I’ll look into whether something on our end caused this. I’ll share another update once I have more information.

5

Might it be related to what I posted recently?

Try your commands with --verbose and see if its stuck in a Sync-reading loop like me

6

Looking at these logs, the build step completed successfully, and the issue occurs during the upload step for dev preview. These seem to be separate issues. I’ll take a look at the issue you’re encountering as well.

7

@keiraarts we have a temporary fix in place for this at the moment. Just a heads up that the CLI snapshot version shared in the other thread is unrelated to this fix.

8

Hi @Paige-Shopify, this issue seems to be back in the CLI.

Can you check this request ID?

Request ID: 2fa1ac20-8a82-42e1-9b35-f71c67f3b94d-1782312509

9

Another request ID: 6b085b02-fb43-4706-b655-d06e0603bf97-1782320690

10

Hi, adding another data point for what looks like the same issue.

Request ID: 4b82d59b-66f7-4c7d-9150-b5af9c36491a-1782320269

The failure is sporadic. I was able to run shopify app dev about an hour ago with the same local setup, but now it fails again.

One interim workaround has been to temporarily remove some toml files where type = "ui_extension", so those extensions are not registered during shopify app dev. Earlier today it worked after removing 3 TOML files, but now I had to remove a 4th one before shopify app dev would start successfully.

I haven’t yet checked whether the removed TOMLs share a specific pattern, such as extension targets or validation config, but I can provide those details if helpful.

Hope this helps!

11

Thanks both for sharing those request IDs. It looks like the temporary fix we had in place is no longer active, which is why this is showing up again. I’ll check whether we can reinstate that mitigation while we work on a permanent fix, and I’ll update this thread once I know more.

12

All sorted now! Please let us know if you continue to encounter any issues.