Redirect resource requires the write_content permission for redirect creation. However, the corresponding GraphQL service requires the write_online_store_navigation permission, which is blocking our migration.
Hi Merchbees,
Just to confirm, the migration is being blocked because you’d need merchants to re-accept the write_online_store_navigation scope that your app didn’t need previously?
Hey @Liam-Shopify,
Yes, you are correct.
We have added the permission for new customers and are also requesting it for existing customers. However, since this is a set-it-and-forget-it type of app, merchants rarely visit the app. We have tested the corresponding GraphQL and are ready to migrate from REST to GraphQL, but doing so would mean halting the service for our existing customers.
It seems that write_content in REST is much more permissive than write_online_store_navigation in GraphQL. It would be great if the development team could provide the write_online_store_navigation permission to those who already have write_content.
Additionally, it’s always challenging to wait for (or email) merchants to log in to the app so we can request approval for new permissions. A suggestion here would be to allow app developers to display a notification to merchants, informing them of pending changes, or to show this information within their Shopify admin login.
Hi again,
Thanks for describing this case, and the challenges with ensuring existing merchants accept the new request. There’s definitely room for improvement here with regard to either notifications or an easier way for existing installs to have scopes auto-enabled. Will connect with the team who owns this area.
1 Like