You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we run eas build --platform android --non-interactive - we still get an error about the metro.config.js that should be bypassed without a prompt. This has not been a problem when we run the build locally, but now that we are trying to automate the builds, it is becoming an blocker.
➜ bitcoin-libre git:(fix/metro-bundler) eas build --platform android --non-interactive --skip-project-configuration
✔ Linked to project @name/name (https://expo.dev/accounts/name/projects/name)
It looks like that you are using a custom metro.config.js that does not extend @expo/metro-config.
This can result in unexpected and hard to debug issues, like missing assets in the production bundle.
We recommend you to abort, fix the metro.config.js, and try again.
Learn more on customizing Metro: https://docs.expo.dev/guides/customizing-metro/
Reproducible demo or steps to reproduce from a blank project
We have tried to use the following metro.config.js - project builds fine with either, but both cause the error to appear even with --non-interactive specified on the eas build command:
bensig
changed the title
eas build shows a metro.config.js error - but the build works correctly when skipped
eas build --non-interactive requires interactions
Sep 24, 2021
bensig
changed the title
eas build --non-interactive requires interactions
eas build --non-interactive requires (certain) interactions
Sep 24, 2021
Summary
When we run
eas build --platform android --non-interactive
- we still get an error about the metro.config.js that should be bypassed without a prompt. This has not been a problem when we run the build locally, but now that we are trying to automate the builds, it is becoming an blocker.Environment
EAS CLI 0.28.2 environment info:
System:
OS: macOS 11.4
Shell: 5.8 - /bin/zsh
Binaries:
Node: 16.9.1 - /opt/homebrew/bin/node
Yarn: 1.22.10 - /opt/homebrew/bin/yarn
npm: 7.21.1 - /opt/homebrew/bin/npm
Utilities:
Git: 2.31.1 - /opt/homebrew/bin/git
npmPackages:
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.13.12 => 0.13.18
npmGlobalPackages:
eas-cli: 0.28.2
expo-cli: 4.11.0
Error output
Reproducible demo or steps to reproduce from a blank project
We have tried to use the following metro.config.js - project builds fine with either, but both cause the error to appear even with
--non-interactive
specified on theeas build
command:The text was updated successfully, but these errors were encountered: