I'm seriously confused with all this talk about channels, branches and whatnot.

How would I do to be able to push changes directly to my production build?

When I do my builds, i just do:

eas build --platform ios --auto-submit

I guess that uses the production setting below?

eas.json

{
  "cli": {
    "version": ">= 3.10.2"
  },
  "build": {
    "development": {
      "developmentClient": true,
      "distribution": "internal",
      "android": {
        "buildType": "apk"
      }
    },
    "development-simulator": {
      "developmentClient": true,
      "distribution": "internal",
      "ios": {
        "simulator": true
      }
    },
    "preview": {
      "distribution": "internal"
    },
    "production": {}
  },
  "submit": {
    "production": {}
  }
}

Hello,

I'm new to React Native and Expo, and I've been exploring the EAS Service. I find the EAS Update feature particularly interesting. From what I understand, it allows you to bypass the traditional process of building, submitting, and waiting for verification from the iOS App Store or Google Play Store.

However, it seems that EAS Update is intended mainly for small bug fixes and minor changes. Is this correct? What prevents us from releasing the app only once on the stores and then using EAS Update to deliver major changes and new versions of the app?

Could someone explain the possible limitations of using EAS Update in this way?

Thanks!