shopify theme pull -e dev using shopify.theme.toml or even passing credentials in with -s and store-handle
I have attempted to shopify auth logout in both the signed in windows and even tried to open new window or browser to login but no dice still and continue to get the error.
Additional info
There are other issues associated with this but appear to be outdated and I’m trying to get to the bottom of whether or not it’s intended behavior to not be able to access theme CLI when shop access is via staff account.
I’m unfamiliar with the bounds, as I often insist on collaborator access but for this shop they didn’t want to mess with it and just made me an administrator with role and group of Senior Admin User in a Organization administrator role. From what I can tell, I have most every permission with the exception of transferring the store.
If this were a collaborator situation, I’d just ask for new roles but at the moment this doesn’t appear to be the case because I have all the permissions it just doesn’t seem as though I can access the shop if I have access has staff - even though it suggests potentially that this is not the case.
I’ve logged in/logged out, accessed the shop by logging in multiple times and logging out (again even in diff windows/browsers).
What type of topic is this
Troubleshooting
Bug report
Feature request
General discussion
Correct - this is one shop (Plus) that has multiple orgs. I’ve been assigned a role managed by Shopify (Organization Administrator) so I can’t see the specific permissions in that view but it says for privileges -
View, create, edit and delete all resources within the organization, along with full access to finance and billing features.
View, create, edit and delete users, roles, and groups.
Assign and remove all roles.
Assign and remove all groups.
Access to all stores and all POS locations within the organization.
In addition to this, I did try and create another staff account with a new role that included development and still can’t access the shop via the CLI. I get the same error after logging out and then trying to log back in with a separate email with the role I created.
I’ve also found so far, it’s just the production shop. The Plus org has a dev, staging, and production shop in the organization. I cannot use the CLI only on the production shop even though all the permissions are the same across the org (from what I can see)
I got this figured out! At some point, the shop changed their myshopify.com store handle. While what I saw in the admin was current-handle it was actually something completely different originally - original-handle
I didn’t see this until I went to open a support request and noticed that the shop name was different and I was trying to figure out what it was tied to. Ran this in the CLI passing the proper handle and no issues so, not linked to staff account issue just the handle wasn’t accessible anywhere that I could find.
Glad to hear you figured it out - I haven’t encountered that issue with old vs new store handles. I’ll see where we can update the docs to highlight this when other devs hit the same issue.
Thanks! Yeah it’s not really surfaced anywhere that I can find except when you go to domains or if you try to open up a support request. Or even if the CLI was er “smart” enough to call this out somehow or identify it’s the wrong handle or at least still reconcile properly that’d obviously be most ideal.
Most of the people working on this project (because it was an acquisition of the brand) had no idea there was even an alt myshopify.com domain to begin with.
so, not linked to staff account issue just the handle wasn’t accessible anywhere that I could find.