EAS Build with RangeError: Invalid string length

[burakgokcinarr]

Build/Submit details page URL

No response

Summary

I'm using EAS Build for a project. But I'm getting the following.

Managed or bare?

Managed

Environment

expo-env-info 2.0.8 environment info:
System:
OS: macOS 13.7.5
Shell: 5.9 - /bin/zsh
Binaries:
Node: 24.12.0 - /usr/local/bin/node
Yarn: 1.22.18 - /usr/local/bin/yarn
npm: 11.6.2 - /usr/local/bin/npm
Watchman: 2024.11.11.00 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.16.2 - /Users/burakgokcinar/.rvm/gems/ruby-2.7.6/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 23.2, iOS 17.2, macOS 14.2, tvOS 17.2, visionOS 1.0, watchOS 10.2
IDEs:
Android Studio: 2024.3 AI-243.26053.27.2432.13536105
Xcode: 15.2/15C500b - /usr/bin/xcodebuild
npmPackages:
expo: ~54.0.29 => 54.0.29
react: 19.1.0 => 19.1.0
react-native: 0.81.5 => 0.81.5
npmGlobalPackages:
eas-cli: 16.28.0
expo-cli: 6.3.12
Expo Workflow: managed

Error output

Compressing project files/usr/local/lib/node_modules/eas-cli/node_modules/@expo/spawn-async/build/spawnAsync.js:19
stdout += data;
^

RangeError: Invalid string length
at Socket. (/usr/local/lib/node_modules/eas-cli/node_modules/@expo/spawn-async/build/spawnAsync.js:19:31)
at Socket.emit (node:events:508:28)
at addChunk (node:internal/streams/readable:559:12)
at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)
at Readable.push (node:internal/streams/readable:390:5)
at Pipe.onStreamRead (node:internal/stream_base_commons:189:23)

Reproducible demo or steps to reproduce from a blank project

eas build --profile development

[burakgokcinarr]

Hello everyone,

I think I've found a solution to the issue I was experiencing, and I'd like to share it here in case it helps anyone else.

First, for my Expo project (managed), I have eas-cli/16.28.0 darwin-x64 node-v24.12.0 versions for build processes (iOS or Android, it doesn't matter).

During the build process, I encountered the error “angeError: Invalid string length.” I noticed that this error was related to issues in Expo's default project settings and/or in the git files from a version originating from Eas cli. Actually, the error indicated that the compressed files were too large, which made me think that the “node_modules” folder might not be ignored. Then I noticed (by chance) that my project didn't have a .git file. So I ran the “git init” command in my project folder and tried building again, and I got a successful build. :)

Hope this helps, or maybe someone else can shed more light on the cause :)

Translated with DeepL.com (free version)