Before a build job can begin compiling your project, all project dependencies need to be available on disk. The longer it takes to acquire the dependencies, the more you need to wait for your build to complete — so caching dependencies is an important part of speeding up your builds.
We're actively working on improving caching and other aspects of the build process in order to make builds reliably fast.
field on build profiles in eas.json
value will invalidate the cache. Changing any other property of the
object will also invalidate the cache.
The caching implementation is built on top of Amazon S3, and it's not fast enough to give you any benefit from caching
node_modules or CocoaPods; it's intended only for files that require significant computation to generate, e.g. compilation results (both final binaries and any intermediate files).
It is not yet possible to save and restore
node_modules between builds.
EAS Build runs a Maven cache server that can speed up downloading Android dependencies for your build jobs.
Currently we are caching:
There is no caching done for CocoaPods dependencies yet, only the
Podfile.lock file is cached (in order provide consistent results across managed app builds).