Shopify / cli

Build apps, themes, and hydrogen storefronts for Shopify
https://shopify.dev
MIT License
422 stars 125 forks source link

[Bug]: Shopify CLI quits 'Dev' command intermittently #4618

Open rcasimmons opened 5 days ago

rcasimmons commented 5 days ago

Please confirm that you have:

In which of these areas are you experiencing a problem?

Theme

Expected behavior

Running the CLI's Dev command should give me a running server that indefinitely runs until I close this myself.

Actual behavior

At random intervals, the CLI will quit running the 'Dev' command and display the following error:

[401] API request unauthorized error: Image

The error appears to be consistent every time the CLI quits the dev command although the interval at which it happens appears to be random with no correlation between files being saved/synced.

I don't current have a --verbose log at hand but will update the issue when this is at hand.

Verbose output

TBC

Reproduction steps

  1. Run the normal shopify theme dev command

Operating System

macOS 14.6.1

Shopify CLI version (check your project's package.json if you're not sure)

3.68.0

Shell

Zsh

Node version (run node -v if you're not sure)

v22

What language and version are you using in your application?

N/A

mgmanzella commented 4 days ago

👋 thanks for reporting this issue, to confirm when did you start experiencing this? was it on this new version of the CLI? also, does this still happen when you use the --legacy flag? this information will help us narrow down the root of the problem. please send along the verbose logs when you have them as well. thanks again 🙏

mgmanzella commented 4 days ago

looks like the team is aware of this and has some in flight fixes, in the meantime let us know if using --legacy is an effective workaround

https://github.com/Shopify/cli/pull/4599 https://github.com/Shopify/cli/pull/4606

rcasimmons commented 7 hours ago

looks like the team is aware of this and has some in flight fixes, in the meantime let us know if using --legacy is an effective workaround

#4599 #4606

Hey!

This hasn't happened with the --legacy flag active.

I updated to 3.68.1 with a supposed fix for 401 but sadly this hasn't worked.

I'm still unable to get you a --verbose log just because there will be times I launch the CLI as is.

I will run the CLI using --verbose today and report back :)