Apps that do not configure their access scopes in the app toml file have accepted access scopes wiped when starting a CLI `dev` session on the Dev platform?

Dev Platform
1

We haven’t yet moved our app’s access scope configuration to the app toml file, and now it looks like our dev config is required to diverge from our production config, which is always a bad idea IMO.

2

Hey this is a known issue and we’re working on a fix right now, sorry for the inconvenience but you can try to re-trigger OAuth for your shop as a work-around for now.

1 Like
3

Thanks for the quick reply - let me know when a fix is out! :folded_hands:

4

Hello, the fix should be out now. You need to re-trigger OAuth from your app to re-request the access scopes on the installed Shop one more time, and subsequent app dev sessions should not overwrite the accepted access scopes. Thanks!

5

Hello,

The issue is still there for me (tried like 5h ago).
I’m on @shopify/cli@3.84.1

7

Can you provide a snippet of your TOML configuration for the [access_scopes] section?

You’ll need to re-trigger OAuth from your app to re-request and accept the access scopes again.

8

I don’t have the [access_scope] section in my TOML files, still on old install flow. Is it now required with the new dev platform?

Also it happened again after I uninstall/reinstall the app.

9

If you don’t have [access_scope]section then you’re defaulted to use Shopify managed install without any scopes (new install flow)

You’ll need to add the explicit setting to use legacy install to your configuration:

[access_scopes]
use_legacy_install_flow = true
10

Interesting, I didn’t had any issue without it previously, is this mandatory since the new dev platform? I won’t have any regressions if I had that to my prod TOML?