EAS build reads your .gitignore file

When building artifacts on EAS, one common issue developers face is accidentally excluding necessary files by adding them to the .gitignore file. Before starting the build process, it’s crucial to double-check that important configuration files—such as app.json, eas.json, or environment variables—are not mistakenly ignored by Git.

To prevent this, thoroughly review your .gitignore file and ensure that any essential project files required for your build aren’t listed there. Ignoring these files can cause your build to fail or miss critical configurations, leading to errors in your production release.

By maintaining a clean and accurate .gitignore, you ensure a smoother EAS build process without unexpected issues.

Keep building!

Comments

[Michael Kochell]

You can also use .easignore which will take precedence over .gitignore, if you have some files you want to provide to the builder that you don't want in your .gitignore file. docs.expo.dev/build-reference/easi...

By default, the EAS CLI refers to the .gitignore file (if it exists) to determine which files to ignore. If you create a .easignore file, the EAS CLI prioritizes it over the .gitignore file. When creating a .easignore file, include all files and directories from your .gitignore file and add additional files you want to ignore.