Any update on this?
+1
I’ve been hitting this one constantly and thought I was going mad. It has prevented me from doing any adding to cart when developing using the local server. Incredibly frustrating.
Im having the same issue and also a never ending errors about “collect” end point
Hey folks, quick update on this.
I followed up with the CLI team internally and they’re actively looking into the 401 regression. A couple of things from that conversation:
First, a correction on the workaround – rather than downgrading CLI versions (which as some of you have found isn’t reliable), the team recommends using the preview URL that shopify theme dev outputs when it starts up (the https://*.myshopify.com URL with the preview_theme_id param) instead of the localhost URL. That should bypass the 401 entirely while this gets sorted.
I’ll update this thread again once I have more to share from the team.
1 Like
HI @Donal-Shopify ,
Thanks for the response. Yes the “preview” route is an option, but it’s really slow development-wise compared to the locale which has hot reloading.
As another person mentioned above, there also seems to be a never-ending of errors in the console with the “Collect” endpoint.
1 Like
I’m running 3.89.0, and getting 401 errors and the /api/collect issue too.
The theme preview isn’t really a solid solution when you’re trying to debug JS etc.
Hi @Donal-Shopify , thanks for following up and checking with the CLI team.
Using the preview URL does avoid the 401, but in practice it’s a pretty big step back for day‑to‑day development. Losing fast local hot reload makes debugging JS and iterative UI work significantly slower, especially on larger themes.
A few additional details that may help the team:
-
The 401 still occurs on CLI
v3.89.0 -
The browser console also gets spammed continuously with errors hitting the
/api/collectendpoint -
This happens even on otherwise unchanged themes that were working fine before
-
Downgrading the CLI hasn’t been reliable across machines
Are there any short‑term alternatives the team can suggest that preserve local hot reload? For example:
-
A CLI flag or env setting to bypass the failing auth check
-
A known stable CLI version that reliably avoids this regression
-
A temporary way to disable or stub the
collectcalls duringshopify theme dev
Happy to provide logs or test a patched build if that helps narrow things down.
Appreciate the transparency so far, and looking forward to any updates.
Thanks!
2 Likes
Yeah this workaround isn’t a great one seeing as we lose hot reloading.
For me theres 3 issues. One the 401 unauthorized (but I don’t experience that on 3.88). Second is the noise from /collect CORS issue. And third is the 429 rate limiting warning I get. Really I don’t see a reason why the rate limit is stricter in dev. If anything, it should be more laxed to allow for us to test add to cart, update cart, etc…
Also curious why bug reports aren’t tracked on Github and we’re brought here. Would be nice to see actual bug reports and be able to follow their progress.
3 Likes
Hey folks - fully hear you re: not having access to local hot reload when using the preview URL. We’re investigating a full fix for this, will update here as soon as there’s more to share.
2 Likes
Interestingly, with Shopify CLI version 3.90.1, I now get the following error when using the /cart/add endpoint with AJAX:
Failed to proxy request to /cart/add with status 502 (Bad Gateway).
URL: https://XXXXXXXXXXXX.myshopify.com/cart/add?_fd=0&pb=0
TypeError: fetch failed
I still get a 401 error with a simple post request or cisting the cart directly.
2 Likes
Sorry to chase, but have Shopify got any update on this yet?
It’s causing a massive headache and bottleneck at the moment, developing interactive parts of themes.
I’ve got same issues, No solution yet…?
This causing massive headache, I can not send a single request to Cart API locally without immediately getting served with a 401. It feels like a core part of CLI is unusable.
1 Like
@Liam-Shopify @Donal-Shopify Any update on this? Almost a month of working around this and not being able to use the CLI for key parts of local theme dev is really starting to become a huge drag on development.
For reference, this is an example of the barrage of console errors I get on any store after booting up the CLI, before I even make any changes. That collect endpoint error is relentless, pings like every 5 seconds.
Happy to share any logs / payloads or anything I can to help move this forwards!
CLI Version: 3.90.1
3 Likes
I’m having the same issues as everyone else, but also keep getting “The access token provided is expired, revoked, malformed, or invalid for other reasons” error every so often. It’s slowing development right down.
1 Like
@Ketan_Mistry That issue is raised here: Shopify Theme Dev > Access Token Expired
@ceri_waters I’ve been having this error ever since these cart ajax issues, so I’m thinking it might be related to something here. I’ve never had this error before otherwise. Fingers crossed it’s all fixed soon!
It appears 3.91.0 may have fixed this now!
I dont believe it has, I upgraded and still getting the same errors
Appears the issue is still there. It did allow me to send 3 requests to cart API this time before blocking me though. Let’s hope a proper fix is not far away…