build failing with "yarn exited with non-zero code: 1"

See original GitHub issue

Summary

Hello all,

My eas cloud builds are failing with the following error: “yarn exited with non-zero code: 1” for both android and iOS.

Running yarn in the root dir of your repository 
yarn install v1.22.10
[1/4] Resolving packages...
[2/4] Fetching packages...
info fsevents@2.3.2: The platform "linux" is incompatible with this module.
info "fsevents@2.3.2" is an optional dependency and failed compatibility check. Excluding it from installation.
[stderr] error eslint@8.2.0: The engine "node" is incompatible with this module. Expected version "^12.22.0 || ^14.17.0 || >=16.0.0". Got "14.15.1"
[stderr] error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
yarn exited with non-zero code: 1

Managed or bare workflow? If you have ios/ or android/ directories in your project, the answer is bare!

managed

What platform(s) does this occur on?

Android, iOS

SDK Version (managed workflow only)

43

Environment

Expo CLI 4.13.0 environment info: System: OS: macOS 11.6 Shell: 5.8 - /bin/zsh Binaries: Node: 16.13.0 - /usr/local/bin/node Yarn: 1.22.15 - ~/.yarn/bin/yarn npm: 8.1.0 - /usr/local/bin/npm Watchman: 2021.10.04.00 - /usr/local/bin/watchman Managers: CocoaPods: 1.10.1 - /usr/local/bin/pod SDKs: iOS SDK: Platforms: DriverKit 21.0.1, iOS 15.0, macOS 12.0, tvOS 15.0, watchOS 8.0 IDEs: Android Studio: 4.1 AI-201.8743.12.41.6858069 Xcode: 13.1/13A1030d - /usr/bin/xcodebuild npmPackages: expo: ~43.0.0 => 43.0.2 react: 17.0.1 => 17.0.1 react-dom: 17.0.1 => 17.0.1 react-native: 0.64.3 => 0.64.3 react-native-web: 0.17.1 => 0.17.1 npmGlobalPackages: expo-cli: 4.13.0 Expo Workflow: managed

Reproducible demo or steps to reproduce from a blank project

I don’t have a reproducible repo for this yet, I am creating it but just wanted to submit the issue incase its a quick and easy fix.

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:5

github_iconTop GitHub Comments

4reactions
MoSattlercommented, Nov 24, 2021

Same problem here - is there any work around?

1reaction
haibertcommented, Nov 13, 2021

I was able to get rid of the issue by uninstalling eslint. Seems like the version I have installed ‘8.2.0’ is not compatible with the version of node expo uses during the build. I guess I will have to downgrade eslint or remove it before builds, correct?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Failed to install expo package with error: yarnpkg exited with ...
This is one way how I solved this issue. I deleted the yarn.lock file & .expo folder and tried running expo upgrade and...
Read more >
Error Codes | Yarn - Package Manager
A list of Yarn's error codes with detailed explanations. ... never has been built before, or its previous build failed (returned a non-zero...
Read more >
Build was terminated: Build script returned non-zero exit code: 1
Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid...
Read more >
Failed to install expo package with error: yarnpkg exited with ...
I tried yarn install as suggested in StackOverflow but did not work. Any ideas what is the problem? Many thanks! wkozyra ...
Read more >
Yarn run error command failed with exit code 1
Container has finished succesfully. for >$ yarn run build. json modified: yarn. Nov 08, 2021 · xcode error: clang++ failed with exit code...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found