npm run deploy new remix project vs old (access scopes wont update)

Shopify Apps

Topic summary

A developer is experiencing inconsistent behavior between a newly created Shopify Remix project (using CLI version 3.57.0) and one built 3 months ago, despite having identical shopify.app.toml files (except for redirect URL and app name).

Key Issue:

  • Access scopes prompt appears when deploying the new project
  • Access scopes do NOT update or prompt on the older project
  • Both projects should theoretically behave the same way

Current Status:

  • The developer is seeking to understand why this discrepancy exists
  • Unable to modify access scopes on the 3-month-old app
  • Images were included (but appear corrupted/unreadable in the post) likely showing the different deployment behaviors

This appears to be an unresolved technical issue with potential implications for app configuration or CLI version differences.

Summarized with AI on November 11. AI used: claude-sonnet-4-5-20250929.
1

I am trying to understand why on a brand new remix project made with the shopify cli (current version 3.57.0) i will get different responses compared to my remix project i made 3 months ago. the shopify.app.toml files look the same for both (besides the redirect and the name of the app)

This is the 3 month old remix project

bguse_0-1710509940697.png
bguse_0-1710509940697.png1005×416 9.73 KB

This is the brand new one today.

bguse_1-1710509962593.png
bguse_1-1710509962593.png1025×637 14.7 KB

just trying to understand why the access scopes will pop up on the new one from today and not the old one. it appears i cant change the access scopes at all for my older app.

Thanks in advanced.