EXPO - EAS build failing
See original GitHub issueCurrent Behavior
Hi, I’m currently migrating two repos to an NX mono repository (React.JS + Expo).
Everything was going well until yesterday. All my EAS builds are failing and I can’t understand why (they worked perfectly fine when I used a standalone repo)
Expected Behavior
The EAS build should be succeeded when using @nrwl/expo:build.
Github Repo
No response
Steps to Reproduce
https://github.com/yonitou/example
- Go to the GitHub repo above
- Run npm install
- nx build native-app --configuration=simulator
- Wait
Nx Report
> NX Report complete - copy this into the issue template
Node : 16.13.1
OS : darwin arm64
npm : 8.3.0
nx : 15.0.13
@nrwl/angular : Not Found
@nrwl/cypress : 15.0.13
@nrwl/detox : 15.1.1
@nrwl/devkit : 15.0.13
@nrwl/esbuild : Not Found
@nrwl/eslint-plugin-nx : 15.0.13
@nrwl/expo : 15.1.1
@nrwl/express : Not Found
@nrwl/jest : 15.1.1
@nrwl/js : 15.0.13
@nrwl/linter : 15.0.13
@nrwl/nest : Not Found
@nrwl/next : Not Found
@nrwl/node : Not Found
@nrwl/nx-cloud : Not Found
@nrwl/nx-plugin : Not Found
@nrwl/react : 15.0.13
@nrwl/react-native : Not Found
@nrwl/rollup : 15.1.1
@nrwl/schematics : Not Found
@nrwl/storybook : 15.0.13
@nrwl/web : 15.1.1
@nrwl/webpack : 15.1.1
@nrwl/workspace : 15.0.13
typescript : 4.8.4
---------------------------------------
Local workspace plugins:
---------------------------------------
Community plugins:
### Failure Logs
```shell
The failure logs provided by EXPO are :
FAILURE: Build failed with an exception.
49
[stderr] * Where:
50
[stderr] Script '/home/expo/workingdir/build/node_modules/@react-native-community/cli-platform-android/native_modules.gradle' line: 250
51
[stderr] * What went wrong:
52
[stderr] A problem occurred evaluating script.
53
[stderr] > Calling `[node, /home/expo/workingdir/build/node_modules/@react-native-community/cli/build/bin.js, config]` finished with an exception. Error message: groovy.json.JsonException: Unable to determine the current character, it is not a string, number, array, or object
54
[stderr]
55
[stderr] The current character read is 'i' with an int value of 105
56
[stderr] Unable to determine the current character, it is not a string, number, array, or object
57
[stderr] line number 1
58
[stderr] index number 0
59
[stderr] info Run CLI with --verbose flag for more details.
60
[stderr] ^. Output: info Run CLI with --verbose flag for more details.
### Additional Information
_No response_
Issue Analytics
- State:
- Created 10 months ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Troubleshooting build errors and crashes - Expo Documentation
Go to your build details page (find it on the build dashboard if you don't have it open already) and expand any failed...
Read more >Android build failed using eas build. · Issue #1101 · expo/eas-cli
I upgraded my expo project to expo 45.0.0 from expo 41.0.0 . While building the project using the command eas build -p android...
Read more >EAS build failed with error code 1 but Expo Build succeeds, i ...
Please do EAS build if you was doing Expo build. This Error will be solved by doing EAS build as it removes the...
Read more >Problems building on eas-cli [resolved] - The Draftbit Community
It was mostly building fine on expo-cli but none of my builds on eas-cli have worked. The error for iOS:
Read more >Expo Eas Local Build Failed : r/reactnative - Reddit
I was giving a chance to expo for the first time today after doing RN bare for ~2 years. Why can't I "npx...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hey ! Thanks for your help.
I just ran nx migrate latest. It worked without any errors but it doesn’t change anything. It really feels like my package-lock.json is kind of corrupted but I deleted it and it changed nothing … I’m running out of ideas, did you have a look on my repository that I shared ? I really need some help 😦
Yes maybe, the thing is I’m not even using expo-status-bar so I don’t know why is it even an issue. Here the steps I had to follow to fix everything :
The builds are now working perfectly but it was a hell of a challenge. I suspect that something is wrong with the package-lock.json. Would be very happy if you have any answers to provide. Here’s my final package.json =>
And my expo package.json :