[FIXED - may require your action] CLI dev/deployment issues

Still have the error on 3.76.2. 3.76.1 works with no issues^

1 Like

You might have some cached values in that version, please run shopify cache clear, that should fix it.

3 Likes

Can confirm running shopify cache clear solves it. Thank you so much!

3 Likes

@Isaac-Shopify I deployed before with 3.76.2 and I lost the permission scopes. I tried to get the collections in a store but it didn’t work.

What should I do here? When I run
shopify cache clear
shopify app deploy

It shows:
ā”ƒ Configuration:
ā”ƒ + access_scopes (new)
ā”ƒ + auth (new)

So I have to get the approval from all users again?

1 Like

Is it on purpose that the cache clear command isn’t documented in shopify commands?

I reverted my production app to a version on last Friday. Then I run shopify app deploy. After deploying, the permissions are retained for the production stores.

I check my users’ stores with access granted. There is no need to grant for permissions. Should be working now.

Now Im getting scope related error after this issue is fixed. Not sure if its related to this bug. I have reinstalled app, checked scopes.

}
client.create error:  {
  errors: {
    topic: [
      'Invalid topic specified: products/create. Does it exist? Is there a missing access scope? Topics allowed: app/uninstalled, shop/update, app_purchases_one_time/update, app_subscriptions/approaching_capped_amount, app_subscriptions/update, domains/create, domains/update, domains/destroy, bulk_operations/finish, shop/redact, customers/redact, customers/data_request'
    ]
  }
}

@Benny_Chan @Murgesh_Ekunde I’m afraid that if you deployed a version that didn’t include any scopes, the next version with scopes will require merchants to re-approve them.

I’ll pass this information to the scopes team to see if there is any way to prevent this specific scenario in the future. I apologize again for the inconveniences this incident created.

EDIT: talked with the scopes team and the scopes issue will affect only merchants that opened your app with the ā€œinvalidā€ version. If you did the rollback to a previous working version, everything should be fine for most if not all merchants.

1 Like

Hi @bkspace, I’m investigating this issue further and wondering if you’d be comfortable sharing your client_id which can be found in the App TOML?