[events]: Required error on shopify app deploy/dev

Extensions
1

Both shopify app deploy and shopify app dev fail immediately with:

╭─ error ──────────────────────────────────────────────────────────────────────╮
│                                                                                │
│  Validation error in shopify.app.<config>.toml:                              │
│                                                                                │
│  [events]: Required                                                          │
│                                                                                │
╰──────────────────────────────────────────────────────────────────────────────╯

Environment

  • Shopify CLI 4.7.0 (also reproduced on 4.6.1 and 4.0.0 via npx @shopify/cli@<version>)
  • Custom app, embedded, with [webhooks], [app_proxy], [access_scopes], [auth], [pos], [sidekick] configured
  • Windows 11

Scope of the issue
Not isolated to one app - every shopify.app.*.toml in our project (7 different app configs) fails identically, including our default shopify.app.toml. None of these apps use the Events subscriptions feature.

What I’ve ruled out

  1. Not stale local config - shopify app config link --client-id <id> pulls the config straight from Shopify’s servers and rewrites the toml. It links successfully but never adds an [events] section, and validation fails again immediately afterward.

  2. Not a recent CLI regression - identical error reproduced via npx @shopify/cli@4.6.1 and npx @shopify/cli@4.0.0.

  3. Not something I can just add by hand - manually adding a bare [events]\napi_version = "unstable" (no subscriptions) flips the error into two contradictory ones at once:

    {
  "issues": [
    { "path": ["events", "subscription"], "message": "Required" },
    { "message": "Unsupported section(s) in app configuration: events" }
  ]
}

    One validation layer demands events.subscription; another simultaneously rejects events as unsupported for this app. That contradiction suggests the schema validator itself has a bug, not that this is a genuine new required feature.

Ask
Is this a known issue, and is there a workaround short of fabricating a fake events.subscription pointing at an endpoint we don’t actually implement?

2

+1, same problem happened for us.
It’s frustrating why unstable Developer preview key has been made mandatory for all apps

3

There is already a thread open on this, closing.

https://community.shopify.dev/t/getting-error-validation-errors-in-shopify-app-toml

5

Hey folks!

Closing the loop here: we’ve released a fix, and the issue is now resolved. Thank you for your patience!