I mentioned this thread to the author of Liquid Ajax Cart, but I don’t think it’s that library that’s the problem. I’ve used it for years without ever experiencing 422. I think rate limits need to be laxed or returned to what they were before.
Hi, it becomes impossible to develop with Ajax functions on the cart with the CLI. All requests on http://127.0.0.1:9292/ result in an error 429. I’m using node v22.15.0 and shopify version 3.88.0. I tried the latest version of shopify CLI (3.91) but I had to rollback because in the latest version the checkout no longer works under development.
@MCP_Webdesign thanks for reporting this to us. Can you share a request ID for any successful cart requests for the same cart in that session so we can investigate further?
This is literally becoming unusable. I can’t go longer than a minute before im seeing 429 and the “Your connection needs to be verified before you can proceed” message. There MUST be a way to be added to a safe list? we are a partner for christ sake, we’re building themes for clients to make you money and your dev tools are woeful.
Hello everyone, thank you for your patience and I appreciate anyone updating the thread if you’re having issues. For those of you that are, the biggest piece of information we can get from you are your verbose logs.
If you run theme dev –verbose we can use that information to help debug. If anyone having trouble is able to do this, you can email me the log directly at josh.faigan@shopify.com along with your store url you are testing on (my-store.myshopify.com).
Hi and thanks for your patience! I appreciate the logs and information. We have identified the root cause and are actively working on a fix. I will update here once we have it. We will also release a snap build to test out.
Good morning everyone, we released a patch for the CLI and the new version is 3.92.1. This should fix the rate limiting issues we’ve been seeing along with the 401 status.
If you are still experiencing problems, please let us know and we can take a look.
@Glenn_Rivermint , we saw this issue creep up over the last month, six months is a long time to have this issue! Is this directly running through theme dev? Would like to get some more information from you around your setup, cli version, etc.