Node 14 error on eas build

Expo Development Tools
1

Hi all:

I’m working with expo for a while now but I’m having issues building my iOS artifact, recently updated to expo 46, and it was working fine with the eas build. (the last time I made a successful build was 15 days ago).

Today I started getting following error in the Install custom tools phase when I run eas build -p ios:

Installing node v14.15.1
Downloading and installing node v14.15.1...
[stderr] 
Downloading https://nodejs.org/dist/v14.15.1/node-v14.15.1-darwin-arm64.tar.xz...
[stderr] 
curl: (22) The requested URL returned error: 404
[stderr] 
Binary download from https://nodejs.org/dist/v14.15.1/node-v14.15.1-darwin-arm64.tar.xz failed, trying source.
[stderr] 
grep: /Users/expo/.nvm/.cache/bin/node-v14.15.1-darwin-arm64/node-v14.15.1-darwin-arm64.tar.xz: No such file or directory
[stderr] 
Provided file to checksum does not exist.
[stderr] 
Binary download failed, trying source.
Detected that you have 2 CPU core(s)
Number of CPU core(s) less than or equal to 2, running in single-threaded mode
Clang v3.5+ detected! CC or CXX not specified, will use Clang as C/C++ compiler!
[stderr] 
Downloading https://nodejs.org/dist/v14.15.1/node-v14.15.1.tar.xz...
[stderr] 
######
[stderr] 
8.6%
[stderr] 
########################
[stderr] 
34.6%
[stderr] 
###########################################                               60.8%
[stderr] 
##############################################################
[stderr] 
86.6%
[stderr] 
######################################################################## 1
[stderr] 
00.0%
[stderr] 
Computing checksum with shasum -a 256
[stderr] 
Checksums matched!
$>./configure --prefix=/Users/expo/.nvm/versions/node/v14.15.1 <
[stderr] 
./configure: line 8: exec: python: not found
[stderr] 
nvm: install v14.15.1 failed!
Failed to install Node.js v14.15.1
bash exited with non-zero code: 1

Here is the output of my eas diagnostics:

  EAS CLI 3.9.3 environment info:
    System:
      OS: Linux 5.15 Ubuntu 20.04.4 LTS (Focal Fossa)
      Shell: 5.0.17 - /bin/bash
    Binaries:
      Node: 14.15.1 - /usr/bin/node
      Yarn: 1.22.18 - /usr/bin/yarn
      npm: 6.14.8 - /usr/bin/npm
    Utilities:
      Git: 2.25.1 - /usr/bin/git
    npmPackages:
      expo: ^46.0.0 => 46.0.17 
      expo-dev-client: ~1.3.1 => 1.3.1 
      expo-updates: ~0.14.7 => 0.14.7 
      react: 18.0.0 => 18.0.0 
      react-dom: 18.0.0 => 18.0.0 
      react-native: 0.69.9 => 0.69.9 
      react-native-web: ~0.18.7 => 0.18.10 
    npmGlobalPackages:
      eas-cli: 3.9.3
      expo-cli: 6.3.2
    Project workflow: generic

The only way to fix it is updating to a newer version of Node? if there another solution I’ll rather go in that direction.

Thanks in advance

2

This is probably a result of a migration to M1 machines, that node version does not have arm support.

You can get back to intel by adding "resourceClass": "intel-medium" in your eas.json, but sooner or latter you will need a switch to M1. Check M1/M2 Migration Timeline for EAS Build | by James Ide | Apr, 2023 | Exposition for more details.

3

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.