I’ve noticed that each of our developer have different dev stores listed in https://dev.shopify.com/dashboard/***/stores. They are seeing old archived stores, as well the active stores they have created. I appear the be the only account who’s seeing the whole list as it was before in the Partner dashboard (all stores that are not archived, created by anyone).
Second point - Now that the Partner dashboard is no longer showing any development stores, how can we archive stores? The new developer interface does not have any buttons to do so.
Store access in the new developer dashboard is on a store by store basis, so you will only see stores where you have access. This is why you as the organization owner have the full list while your staff may not.
As an organization owner, I still cannot see the full list of stores — this might be a bug on your side. Is there any workaround, such as a setting in the Teams section or a plan to restore access to all team members as before?
It doesn’t make sense to send invitations for every single development store when there are issues between our QC and Dev teams. Currently, I only see an option in the Partner section to grant access to specific stores for each team member. However, since I’m the only one with access to the Teams section, this is a highly time-consuming task, and I’m looking for a smarter solution.
Great follow up @Vairo_Team, I’ll need to correct myself here. Currently you will only see the stores that you are the owner of, or a staff on. For stores that are not showing, those would have been created by someone else and you will need to be added to the store.
We are aware that this is not ideal in it’s current state.
Unfortunately once we did this shops’ access scopes were all lost. This is a MAJOR bug. Thankfully this was on our development app but would have resulted in serious harm if in production.
We brought this issue to Shopify Partner support and they keep insisting that we need to use shopify.toml to manage app scopes. This is just not true and unfortunately reflects a long history of Shopify Support (starting with metafield definition/metafield conflicts) telling us wrong information or to do needless things that would be arduous and/or detrimental to our business.
Posting here to let others know that “migrating” to the dev dashboard can result in catastrophic errors for your application and while the Shopify support conversation is ongoing, it needs to be made clear either to the Shopify development community or to internal staff that managing access scopes via shopify.toml is or is not mandatory. Currently it’s pretty clear that it’s optional, i.e. want to use a “managed installation” but Shopify support insists otherwise.
Hey @sshaw, thanks for reporting that here. I’m happy to dig in to this so we have some clarity in the community on what is expected and I can make sure any issues are brought to our team.
Going solely off of the migration documentation you shared, using the CLI and app configuration files is required when working with extensions. If you’re not using extensions, then it wouldn’t be necessary.
If your app has extensions, then you’ll need to take additional steps after Shopify migrates you to the Dev Dashboard. Your current installations will continue to function, but to keep building and updating post-migration, you will need to:
If you see unexpected configuration changes when running shopify app deploy , then your shopify.app.toml may not be up to date with values set using your dashboard.
If you’re seeing different behaviour, can you share some specifics on your configuration so that I can replicate this to see if I get the same.
It is mandatory for extensions yes but that is not the problem. The problem we do not use it for managing access scopes. Every time we have deployed our extension access scopes were not affected. After this migration email, when we deployed the extension, it removed all access scopes for the app! We use the Shopify App Ruby gem for managing access scopes and do not want to use the CLI for this. Access scopes are not applied uniformly for stores and depend on app plan and other things. We are not going to request customer-related permissions for a store that does not pay for us to do something with these customers.
Thanks for sharing that @sshaw. I’m getting a better picture now of what you’re seeing. I’m going to take a look here to see what I can find out for you.