Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unexpected server error on Android buils #2314

Closed
Noxel opened this issue Apr 5, 2024 · 11 comments
Closed

Unexpected server error on Android buils #2314

Noxel opened this issue Apr 5, 2024 · 11 comments
Labels
eas build needs review Issue is ready to be reviewed by a maintainer

Comments

@Noxel
Copy link

Noxel commented Apr 5, 2024

Build/Submit details page URL

No response

Summary

Hi, just wanted to make a fix on an app in expo 49 but can't build it. I have no idea what's the problems. I search at my side on compare this project with other that i can build with eas-cli but could not find a difference.
It happend for a week now.

I have post a message at the discord server.

Managed or bare?

bare

Environment

✔ Check Expo config for common issues
✔ Check package.json for common issues
✔ Check dependencies for packages that should not be installed directly
✖ Check native tooling versions
✔ Check npm/ yarn versions
✔ Check for issues with metro config
✖ Check for common project setup issues
✔ Check Expo config (app.json/ app.config.js) schema
✔ Check that packages match versions required by installed Expo SDK
✔ Check for legacy global CLI installed locally
✔ Check that native modules do not use incompatible support packages
✖ Check that native modules use compatible support package versions for installed Expo SDK
Detailed check results:
Expected package @expo/config-plugins@~7.2.2
Found invalid:
@expo/[email protected]
@expo/[email protected]
@expo/[email protected]
(for more info, run: npm why @expo/config-plugins)
Advice: Upgrade dependencies that are using the invalid package versions0.
This project has native project folders but is also configured to use Prebuild. EAS Build will not sync your native configuration if the ios or android folders are present. Add these folders to your .gitignore file if you intend to use prebuild (aka "managed" workflow).
Cocoapods version check failed. Cocoapods may not be installed or there may be an issue with your Cocoapods installation. Installing version 1.15.2 or higher is recommended.
One or more checks failed, indicating possible issues with the project.

Error output

Starting Android build

[
  {
    "extensions": {
      "requestId": "922[68](https://gitlab.ci.novadys.cloud/dev/novatime/mobile/intervenants/-/jobs/266042#L68)9c9-9ac3-4f20-be2f-ace00cee5[71](https://gitlab.ci.novadys.cloud/dev/novatime/mobile/intervenants/-/jobs/266042#L71)3",
      "code": "INTERNAL_SERVER_ERROR",
      "errorCode": "EAS_BUILD_DOWN",
      "metadata": {},
      "isTransient": false
    },
    "message": "Unexpected server error (Expo error ID: 922689c9-9ac3-4f20-be2f-ace00cee5713).",
    "locations": [
      {
        "line": 3,
        "column": 5
      }
    ],
    "path": [
      "build",
      "createAndroidBuild"
    ]
  }
]

Build request failed. Make sure you are using the latest eas-cli version. If the problem persists, report the issue.
Request ID: 9226[89](https://gitlab.ci.novadys.cloud/dev/novatime/mobile/intervenants/-/jobs/266042#L89)c9-9ac3-4f20-be2f-ace00cee5713
Error message: Unexpected server error (Expo error ID: 922689c9-9ac3-4f20-be2f-ace00cee5713).
Error: Build request failed. Make sure you are using the latest eas-cli version. If the problem persists, report the issue.
Request ID: 922689c9-9ac3-4f20-be2f-ace00cee5713
Error message: Unexpected server error (Expo error ID: 922689c9-9ac3-4f20-be2f-ace00cee5713).
    at handleBuildRequestError (/root/.npm/_npx/e25a38a8cc65d08e/node_modules/eas-cli/build/build/build.js:147:15)
    at /root/.npm/_npx/e25a38a8cc65d08e/node_modules/eas-cli/build/build/build.js:100:17
    at process.processTicksAndRejections (node:internal/process/task_queues:[95](https://gitlab.ci.novadys.cloud/dev/novatime/mobile/intervenants/-/jobs/266042#L95):5)
    at async startBuildAsync (/root/.npm/_npx/e25a38a8cc65d08e/node_modules/eas-cli/build/build/runBuildAndSubmit.js:261:12)
    at async prepareAndStartBuildAsync (/root/.npm/_npx/e25a38a8cc65d08e/node_modules/eas-cli/build/build/runBuildAndSubmit.js:247:19)
    at async runBuildAndSubmitAsync (/root/.npm/_npx/e25a38a8cc65d08e/node_modules/eas-cli/build/build/runBuildAndSubmit.js:88:49)
    at async Build.runAsync (/root/.npm/_npx/e25a38a8cc65d08e/node_modules/eas-cli/build/commands/build/index.js:41:9)
    at async Build._run (/root/.npm/_npx/e25a38a8cc65d08e/node_modules/@oclif/core/lib/command.js:80:22)
    at async Config.runCommand (/root/.npm/_npx/e25a38a8cc65d08e/node_modules/@oclif/core/lib/config/config.js:301:25)
    Error: build command failed.

Reproducible demo or steps to reproduce from a blank project

One on my project has this problem on every build or the last week but other projects are fine.

I juste do a npx eas-cli build --pofile prod --platform android --non-interactive

@Noxel Noxel added the needs review Issue is ready to be reviewed by a maintainer label Apr 5, 2024
@szdziedzic
Copy link
Member

You use the latest EAS CLI version, right?

@Noxel
Copy link
Author

Noxel commented Apr 7, 2024

You use the latest EAS CLI version, right?

The latest EAS CLI with npx

@szdziedzic
Copy link
Member

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

@szdziedzic
Copy link
Member

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
Copy link
Author

Noxel commented Apr 10, 2024

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
Copy link
Member

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.

image

@Noxel
Copy link
Author

Noxel commented Apr 17, 2024

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
Copy link

wodin commented Apr 18, 2024

@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
Copy link
Author

Noxel commented Apr 23, 2024

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.

@RalfiBahar
Copy link

Having the same issue. Is there a solution?

@Noxel
Copy link
Author

Noxel commented Aug 28, 2024

My problem resolved itself. I was unable to identify what was blocking the build from being sent.

@Noxel Noxel closed this as completed Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
eas build needs review Issue is ready to be reviewed by a maintainer
Projects
None yet
Development

No branches or pull requests

4 participants