I am trying to create my first eas build and may just be missing something but whenever I run eas build --platform ios, all the credentials are prepared successfully, and then I just receive an error stating: ‘Error: git exited with non-zero code: 128’ and nothing else.
eas-cli/0.17.0 win32-x64 node-v12.18.3
Output after eas build --platform ios
Expo CLI 4.5.2 environment info:
OS: Windows 10 10.0.17763
Node: 12.18.3 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.5 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 6.14.6 - C:\Program Files\nodejs\npm.CMD
Android Studio: Version 220.127.116.11 AI-193.6918.104.22.16814223
expo: ~41.0.1 => 41.0.1
react: 16.13.1 => 16.13.1
react-dom: 16.13.1 => 16.13.1
react-native: https://github.com/expo/react-native/archive/sdk-41.0.0.tar.gz => 0.63.2
react-native-web: ^0.16.3 => 0.16.3
Expo Workflow: managed
I suspect you do not have your code in a Git repository? As far as I know, EAS requires that.
Hello, I do, it’s in an Azure DevOps repos. I’m authenticated with this machine through GitHub desktop to that repos and everything git side with the repos outside of expo is working as expected
We run a couple of Git commands before and during the build. If you can try them out on your machine, you might be able to trace the failing git command. We probably need to add more logging to help to debug this.
Detecting if Git is installed
$ git --help
Does the project belong to a Git repository
$ git rev-parse --git-dir
Are there uncommitted changes
$ git status -s -uall
Copy the repository to a temporary folder, to prepare a tarball to use
$ git clone --no-hardlinks --depth 1 <GIT_PATH> <TEMP_PATH>
GIT_PATH is the full path of your repository, e.g.
TEMP_PATH is a temporary created path, using a folder name of
After these Git commands we create a tarball of the cloned shallow repo and send it to our servers to build your app. Let me know if you can try this out and/or running into an issue with either one of these commands!
I attempted to run all these commands and then all ran without an error but 4 had a warning.
- returned: standard help output
- returned: .git
- returned: nothing
Cloning into ‘C:\Test’…
warning: --depth is ignored in local clones; use file:// instead.
Not sure it would cause any issues by my repos name does have %20’s in the name where spaces were used on creation: i.e: C:\Git\My%20Test%20Repos\
This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.