Authenticate with Mach Dashboard, then link your project. This creates a `mach.config.json` in your root and connects it to the dashboard for builds, secrets, and credentials.
Using more than one account? CLI 2.12.0 and later keep your saved logins. Run mach accounts to list them, mach switch to choose one for this project folder, and mach me to check the selected identity. The CLI Reference explains account preferences and CI token priority.
Each build has a read-only Delivery overview linking its build result, recorded tests and client feedback. Store submission appears only for mobile builds intended for store delivery, excluding simulators and development clients. A completed store upload does not mean the store approved or published the app. Charges are not displayed on the build details page.
In the client portal, administrators can add version-specific release notes and optionally allow guest feedback when creating or updating a guest link. Feedback stays attached to the exact shared build. Guest names are unverified, and approval never submits or publishes an app. Feedback is off by default; rotating, expiring or revoking the link stops further feedback through it. Previous feedback stays in the administrator-only sharing dialog.
Use local builds to test native modules, Flutter plugins, or UI changes before using a cloud runner. Expo projects can use Dev Clients, while Flutter projects run their configured SDK, flavor, target, and mode. Mach injects the selected environment automatically.
mach build --platform ios --local --build-profile development
