Password not working in development store

Topic summary

A developer cannot access their development store despite entering the correct password. When the correct password is entered, nothing happens; when an incorrect password is entered, the system properly validates it as wrong.

Suggested troubleshooting steps:

  • Clear browser cache and cookies, then completely reboot the browser
  • Test in different browsers, incognito/private windows
  • Try different devices (computer, mobile phone)
  • Use the Shopify Mobile app to rule out device-specific issues

Current status:

  • Another user confirmed the password protection is working (tested with “123456” and received expected failure)
  • The issue appears to be a caching problem on the original poster’s end
  • If troubleshooting fails, contacting Partner Support through the Partner dashboard is recommended
Summarized with AI on November 24. AI used: claude-sonnet-4-5-20250929.

I am working on this store, but somehow the password is not working.

If I use a wrong password it validates it ok and tells me it is wrong, but if i enter the correct password, nothing happens ¿any idea why?

Hi, @clausilva .

Thanks for reaching out and posting your question to the Shopify Community.

If I understand correctly, when entering the correct password on the storefront, it does not redirect you to the store.

Are you able to try these troubleshooting steps to see if the issue persists:

If you’re still experiencing a store password issue after trying the above steps, I encourage you to use the Support > Contact Partner Support option within your Partner dashboard.

Lastly, I’d like to share some helpful partner resources if you haven’t come across them yet. Our Partner Blog offers free to access educational resources, developer preview environments, and recurring revenue share opportunities.

I hope this helps!

I tried to access your store with password 123456 and it failed (as I expected/hoped :slightly_smiling_face: ) see snip below

As suggested by other reply you might have a caching issue

Regards

Peter