Expo CLI
expoAn open-source framework for making universal native apps with React.
An open-source framework for making universal native apps with React.
auth.sessionSecretThe rest of the file syncs. Only these values are lifted out and kept in your secret store.
uuiddevelopmentCodeSigningIdPATHOtty splits these out before upload and puts each machine’s own back on the way down — no templates to write.
Nothing. Expo CLI writes no caches or state in your home directory.
uuiddevelopmentCodeSigningIdPATH "username": "octocat", "currentConnection": "Browser-Flow-Authentication" }, "uuid": "8f0c1d2e-0000-4000-8000-000000000000",machine-local "developmentCodeSigningId": "9A1B2C3D4E",machine-local "PATH": "/opt/homebrew/bin:/usr/local/bin:/usr/bin:/bin",machine-local "ignoreBundledBinaries": ["watchman"]}Each machine keeps its own copy of these.
auth.sessionSecretLifted into your secret store; the rest of the file syncs.
Only what the catalog names. A directory that syncs brings everything inside it except what is listed as excluded here.
Opens otty://sync/add/expo. Otty ships with this catalog, so the link only has to name the tool — nothing is downloaded.
Every one of these is generated from the same rules as this page. None of them splits uuid and developmentCodeSigningId for you — that part is Otty’s own sync, or a template you write by hand.