Failed to upload the project tarball to EAS Build

Hello everyone I’m new here . I have an issue When attempting to run ‘eas build --profile preview --platform android’ for a managed workflow project with eas-cli version 6.1.0, I encountered an error while trying to upload the project tarball to EAS Build. The error message is: 'Failed to upload the project tarball to EAS Build. Reason: request to [URL] failed, reason: read ECONNRESET. I’ve already tried disabling the firewall and running expo-doctor, but the issue persists. How can I resolve this upload error and successfully perform the ‘eas build’ command for my managed workflow project?

long error message :

Failed to upload the project tarball to EAS Build

Reason: request to https://storage.googleapis.com/turtle-v2-projects/production/ecbb8539-af01-406f-a888-544c8dd0693e/62da530e-a305-4e04-b3b9-8fe095ba3e81?X-Goog-Algorithm=GOOG4-RSA-SHA256&X-Goog-Credential=www-production%40exponentjs.iam.gserviceaccount.com%2F20230730%2Fauto%2Fstorage%2Fgoog4_request&X-Goog-Date=20230730T172654Z&X-Goog-Expires=3601&X-Goog-SignedHeaders=host%3Bx-goog-content-length-range&X-Goog-Signature=a4eaefc7e5d5bcf5162778ec5e8a9039886c6a615a96805b47649881ff01fa5cb797f7eed646ae73692ef7cd218277ebd9f617d3e62f4d84c46ba65261f7e429efb4025061a0270d376b9374e2c3529d3a1f6f59976a6a2f15a83999e6367ec4e5bf14714d24b262de8e03b626e84cbb686e3fb2f58711b0f872d093b6bd2415d4156435741952976f638b45a2de21f27d2657753b363e4dc1f0d545f06f3e5f145ab042aaffcbedb9c4905c09c894137ba53febb1b8c3726dbb54ca034c19c84c9bcb28d6bdc50b737d6c6d02c34b6f25a2c1eb7742411b2ee1b45a903d5be25f94e3539f377ddffa5ad68def8c3c26f904f6e6cbdaf7a04b3c90d2c43f26b6 failed, reason: read ECONNRESET
Error: build command failed.

May I ask if this problem has been resolved? I have also encountered the same problem

I too have this problem but instead is trying to access my trash

Error message:

Compressing project files and uploading to EAS Build. Learn more: https://expo.fyi/eas-build-archive

Failed to upload the project tarball to EAS Build

I fixed my issue using

git init
git add .
git commit -m "Initial commit"

For some reason, expo acts differently when this is present.

The solution I found to the problem is to build the APK or AAB using GitHub Actions. Until now, I haven’t found any other solution, and I’m unsure how long it will take to resolve this issue.

I tried your solution its still not working at my end

I’ve tried it too, but it still doesn’t work

Try creating a file in your root and call it “.easignore”

Add the following;

# .easignore node_modules npm-debug.log yarn-error.log