Unexpected server error on Android buils about eas-cli

[szdziedzic]

You use the latest EAS CLI version, right?

[Noxel]

You use the latest EAS CLI version, right?

The latest EAS CLI with npx

[szdziedzic]

Interesting, I can't see anything super helpful in our internal logs. Can you show me what your eas.json looks like?

[szdziedzic]

What has changed in your project between the moment you created the last successful build and now? It might be helpful context for me.

[Noxel]

Here's my eas.json :

  "build": {
    "prod": {
      "android": {
        "image": "latest",
        "env": {
          "REACT_NATIVE_API_URL": "URL",
          "REACT_NATIVE_PUBLIC_URL": "URL",
          "REACT_NATIVE_BUILD_PROFILE": "prod"
        }
      },
      "ios": {
        "env": {
          "REACT_NATIVE_API_URL": "URL",
          "REACT_NATIVE_PUBLIC_URL": "URL"
        }
      },
      "credentialsSource": "local"
    },
    "pp": {
      "android": {
        "image": "latest",
        "env": {
          "REACT_NATIVE_API_URL": "URL",
          "REACT_NATIVE_PUBLIC_URL": "URL"
        },
        "buildType": "apk"
      },
      "ios": {
        "env": {
          "REACT_NATIVE_API_URL": "URL",
          "REACT_NATIVE_PUBLIC_URL": "URL"
        }
      },
      "credentialsSource": "local",
      "distribution": "internal"
    },
    "test": {
      "android": {
        "image": "latest",
        "env": {
          "REACT_NATIVE_API_URL": "URL",
          "REACT_NATIVE_PUBLIC_URL": "URL"
        },
        "buildType": "apk"
      },
      "ios": {
        "env": {
          "REACT_NATIVE_API_URL": "URL",
          "REACT_NATIVE_PUBLIC_URL": "URL"
        }
      },
      "credentialsSource": "local",
      "distribution": "internal"
    }
  }
}

Last successful build was Jan 11, 2024 10:55 AM.
First build request failed was Apr 2, 2024 12:10 PM.

I have adding react-native-date-picker and its implementation, i previously was using @react-native-community/datetimepicker.

[szdziedzic]

Hi there @Noxel,

I think I know what's wrong. It seems like you have a disallowed unicode character in the build job's node version value. There are 2 ways to set the node value:

1. directly in eas.json by using the node field
2. by having a .nvmrc file in your project dir (we read the version from there by default)

Do you use any of these by any chance?

Removing this character should solve the issue. I will try to make the error message better as a follow-up. We validate the build job in EAS CLI before sending it to EAS servers, so I'm confused why your node version passed the validation.

[Noxel]

Hi @szdziedzic,

Unfortunately we don't use any of these, i try to affect a value to the node field directly in eas.json but it doesn't change the outcome of the build request.

In fact we use the version 18 of node for our pipeline, so I don't know where the buildEnvironment took this version fo node.

How can we detect some false information in the build job send to EAS ?

[wodin]

@Noxel what do you get if you run the command shown here to see what will get uploaded to the build servers:
https://github.com/expo/fyi/blob/main/eas-build-archive.md#what-files-are-included-in-the-archive

Then search in those files for 20.9?

e.g. grep -rl '20\.9' ~/target/output/path

[Noxel]

Hi @wodin sorry for the late response.
I did search for 20.9 in my local and when the pipeline executes eas build but couldn't find anything.