Where Does fastlane Keep Fastfiles and Metadata?
fastlane lives in a fastlane folder in your repo: Fastfile, Appfile, Matchfile, metadata and screenshots. Layout and sharing rules.
Last updated
fastlane stores everything inside your repository. The fastlane folder holds the Fastfile (lanes), Appfile (identifiers and teams), Matchfile (signing source), plus deliver metadata and screenshots per locale. Run commands from the repo root or the fastlane subfolder; user code executes inside fastlane while actions run at the root.
Commit the Fastfile, Appfile, Matchfile and metadata, but not screenshots: they bloat the repo for no automation gain. match keeps certs and profiles in its own git repo or bucket with certs and profiles folders. Override metadata and screenshot paths per lane when one layout must serve both stores.
Where Fastlane stores this, by platform
<project root>/fastlane/Fastfile
Lanes live here with Appfile and Matchfile beside them. deliver reads fastlane/metadata and fastlane/screenshots per locale. fastlane run ... executes from the repo root, user code from fastlane.
<project root>/fastlane/Fastfile
Same repo-relative layout, used mostly for Android supply lanes and CI. Matchfile certs and profiles folders live in the separate match repo, not here.
<project root>\fastlane\Fastfile
Same structure for Windows CI agents running Android lanes. iOS lanes need macOS regardless of where the files are checked out.
Frequently asked questions
What fastlane files should I commit to git?
Fastfile, Appfile, Matchfile, Deliverfile/Gymfile/Supplyfile and the metadata text files. Exclude screenshots and app previews. Keep signing assets in the separate match repo, never in the app repo.
Where does fastlane match store certificates?
In its own git repository or cloud bucket with certs and profiles folders plus a README. Point Matchfile at it once per team. Lanes fetch fresh copies with match before every gym build.
Notice an outdated path? Let us know.