Closed Ramon-Balaguer closed 2 months ago
{
"name": "XXXXXX",
"version": "1.0.0",
"main": "expo/AppEntry.js",
"scripts": {
"start": "expo start --dev-client",
"android": "expo run:android",
"ios": "expo run:ios",
"web": "expo start --web",
"lint": "eslint ."
},
"dependencies": {
"@expo/metro-runtime": "~3.2.1",
"@gluestack-style/react": "^1.0.56",
"@gluestack-ui/config": "^1.1.18",
"@gluestack-ui/themed": "^1.1.31",
"@gorhom/bottom-sheet": "^5.0.0-alpha.10",
"@react-native-async-storage/async-storage": "^1.23.1",
"@react-navigation/drawer": "^6.6.15",
"@react-navigation/native-stack": "^6.10.0",
"dotenv": "^16.4.5",
"expo": "~51.0.22",
"expo-auth-session": "^5.5.2",
"expo-crypto": "^13.0.2",
"expo-dev-client": "~4.0.20",
"expo-linking": "^6.3.1",
"expo-secure-store": "~13.0.2",
"expo-status-bar": "~1.12.1",
"expo-web-browser": "^13.0.3",
"jwt-decode": "^4.0.0",
"neumorphic-tab": "^1.0.2",
"react": "18.2.0",
"react-dom": "18.2.0",
"react-native": "0.74.3",
"react-native-gesture-handler": "~2.16.1",
"react-native-paper": "^5.12.3",
"react-native-reanimated": "~3.10.1",
"react-native-safe-area-context": "4.10.5",
"react-native-screens": "3.31.1",
"react-native-svg": "15.2.0",
"react-native-vector-icons": "^10.1.0",
"react-native-video": "github:Ramon-Balaguer/react-native-video",
"react-native-web": "~0.19.10"
},
"devDependencies": {
"@babel/core": "^7.20.0",
"@expo/config-plugins": "~8.0.0",
"@expo/prebuild-config": "^7.0.7",
"@types/react": "~18.2.79",
"@types/react-native-vector-icons": "^6.4.18",
"eslint": "^8.57.0",
"eslint-config-expo": "^7.0.0",
"eslint-config-prettier": "^9.1.0",
"eslint-plugin-prettier": "^5.1.3",
"prettier": "^3.3.2",
"typescript": "~5.3.3"
},
"private": true
}
I'm wondering how the RUN npx eas build --platform android --local --profile production
call worked for you 🤔. What I mean by this is that you are calling the eas
package here and not eas-cli. The eas
package is not associated with Expo and EAS CLI. The correct way to use EAS CLI through the npx is to do npx -y eas-cli@latest ...
instead of npx eas ...
.
You shouldn't install Expo CLI globally anymore, it's shipped with an expo
package (you can call it as npx expo ...
) and you are using both eas-cli
and expo-doctor
through npx anyway so this line can be changed to:
npm i -g expo-cli eas-cli expo-doctor npx
-> npm i -g npx
or even deleted if npx
is shipped in the base image by default.
I believe that COPY . .
instruction will copy all files and directories from the current directory on the host machine into the current working directory in the Docker image. It means it will also copy your node_modules
if not dockerignored and it might be problematic. Do you have node_modules
dockerignored?
ENV EXPO_TOKEN
- I hope this wasn't your real token. If it was please disable it.
This issue is stale because it has been open for 30 days with no activity. If there is no activity in the next 7 days, the issue will be closed.
This issue was closed because it has been inactive for 7 days since being marked as stale. Please open a new issue if you believe you are encountering a related problem.
Build/Submit details page URL
No response
Summary
I try to use docker to execute: npx eas build --platform android --local --profile production
My docker file:
All works good but when script try to execute last RUN
Managed or bare?
bare
Environment
RUN npx expo prebuild
RUN npx expo-doctor RUN git init RUN npx eas build --platform android --local --profile production
Error output
Reproducible demo or steps to reproduce from a blank project
docker build -t project . docker run project