This command requires Expo CLI.

Hi all.
when i try to launch the build for android in the dashboard i receive this message
This command requires Expo CLI. as you can see from the image in attachment.
The build is blocked in this point. What can i do ?
thanks a lot to all

Hi @eva_energy_service

What does the Run expo doctor section show?

Also, what do you get if you run npx expo-env-info?

And what do you have in your eas.json file? And the scripts section of package.json?

my package json is

  "main": "node_modules/expo/AppEntry.js",
  "scripts": {
    "start": "expo start",
    "android": "expo start --android",
    "ios": "expo start --ios",
    "web": "expo start --web",
    "eject": "expo eject"
  "dependencies": {
    "@react-native-community/cookies": "^5.0.1",
    "@react-native-community/netinfo": "^5.9.10",
    "expo": "~40.0.0",
    "expo-app-loading": "^1.0.1",
    "expo-status-bar": "~1.0.3",
    "expo-updates": "~0.4.1",
    "metro-core": "^0.58.0",
    "react": "16.13.1",
    "react-dom": "16.13.1",
    "react-native": "",
    "react-native-fs": "^2.16.6",
    "react-native-loading-spinner-overlay": "git+",
    "react-native-svg": "^12.1.0",
    "react-native-web": "~0.13.12",
    "react-native-webview": "^11.0.2"
  "devDependencies": {
    "@babel/core": "~7.9.0"
  "private": true

my eas.json is:

  "cli": {
    "version": ">= 5.4.0"
  "build": {
    "development": {
      "expoCli": "6.0.8",
      "developmentClient": true,
      "distribution": "internal"
    "preview": {
      "distribution": "internal"
    "production": {}
  "submit": {
    "production": {}

expo doctor shows me this:

OK, I believe this is the main problem. EAS Build supports Expo SDK 41 and later

i try to update to 41 version but i have the same problem

hi there! you should update to a more recent sdk version. at any given time, we actively support the 3 most recent sdk releases (currently: 47, 48, 49) - this covers all releases over a ~1 year period. beyond that window, it is difficult for us to help because the tooling will be rather out of date.

ok thanks to all, it goes ahead but i receive a new error that you can see in the image below

Based on the above I assume you’re on the Bare workflow?

Do have any of your own custom changes to the android or ios directories?

If not, I suggest you delete them to switch back to the managed workflow.

If you upgrade to Expo SDK 49, you’ll need to get rid of this. As per the Expo SDK 45 release blog post:

expo-app-loading is deprecated — use expo-splash-screen directly instead: SplashScreen.preventAutoHideAsync() and SplashScreen.hideAsync(). The implementation is only a thin wrapper around expo-splash-screen that you can copy into your project if you’d like to keep using it.

This doesn’t look like something you should have installed.

The complaint about the minSdkVersion: It looks like you have it in Instead, you’d need to install expo-build-properties and add it to the plugins section of your app.json. See the BuildProperties docs for an example.

You can remove sdkVersion from app.json.

You shouldn’t have those @unimodules/* packages installed, but they are probably there because of other dependencies. What does your package.json look like now?