Shopify CLI Error: Store without active password can’t start theme development mode

Hi everyone,

I’m encountering an issue when trying to use Shopify CLI to start the theme development mode. The error says that my store password is incorrect, but the password protection is not active. This is preventing the development environment from launching successfully. I’ve tested this with version latest version (3.69.0)

Here’s the command I’m using:

shopify theme dev

You can also find the error details in the attached screenshot below.

Has anyone experienced this issue before? Any suggestions on how to resolve this?

Thanks in advance for your help!

Hi Hasan - just to confirm, this store is not a development store, correct? If you test with a different store, are you seeing the same error message?

1 Like

Hi Liam,
No, this is not a development store; it’s a live store.

Thank you for your response!

Hey Hasan!

You may be able to try specifying the shop via the --store flag.

If that doesn’t resolve the issue, please open a bug report here so one of us can take a deeper look.

Thanks!

2 Likes

Hey James,

I tried using the --store flag as you mentioned, but unfortunately, I’m still encountering the same issue. I’ve gone ahead and submitted a bug report, which you can view here:

Thanks again for your help, and I appreciate your team looking into this!

1 Like

Hi again @James-Shopify
Do you have an estimate on when this issue might be resolved? Unfortunately, it’s making our work quite challenging.

Hey Hasan!

Thanks for your patience - I responded on the github issue you opened.

I will need your help to gather some information before I can determine what the required fix is / before I can provide an estimate of a timeline.

I will try my best to unblock you or help you find a workaround

1 Like

Hey @James-Shopify

Thank you for following up! I’ve provided the necessary information on GitHub as requested. Let me know if there’s anything else you need from my side.

I appreciate your help in unblocking this issue and exploring potential workarounds!