EAS Android build fails: timeout from maven.production.caches.eas-build.internal
- Dominant language
- TypeScript
- Stars
- 1.4k
- Forks
- 236
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 91
Description
### Build/Submit details page URL
_No response_
### Summary
Android EAS builds are failing during Gradle dependency resolution.
Error:
Could not GET 'http://maven.production.caches.eas-build.internal/...'
Read timed out while resolving:
org.jfrog.buildinfo:build-info-extractor-gradle:5.2.5
Reproducible across retries.
Builds fail early and quota is not consumed.
Likely Expo internal Maven/Artifactory cache issue.
EAS CLI: latest
Workflow: managed/bare (specify)
### Managed or bare?
Android
### Environment
Expo EAS Build (cloud)
Workflow: Managed
Platform: Android
EAS CLI: latest
OS: Linux (Expo build worker)
### Error output
_No response_
### Reproducible demo or steps to reproduce from a blank project
Yes. Reproducible from a blank managed Expo project.
Steps:
1. Create a new managed Expo project (npx create-expo-app).
2. Run eas build -p android.
3. Build fails during Gradle dependency resolution with timeout from
maven.production.caches.eas-build.internal while resolving
org.jfrog.buildinfo:build-info-extractor-gradle:5.2.5.
Contributor guide
Assessment
This issue has not been assessed yet.