Setup

What happens when you plug a phone in, and the taps only a person can do.

Plug it in

  1. Connect the phone to the Mac by USB and unlock it

    Use a data cable. A charge-only cable shows nothing on the Mac.

  2. Tap Trust

    The phone asks once whether to trust this computer.

  3. Turn the passcode off

    Settings › Face ID (or Touch ID) & Passcode › Turn Passcode Off. With a passcode on, iOS stops the runner with "Timed out while enabling automation mode".

  4. Turn on Developer Mode

    Settings › Privacy & Security › Developer Mode. The phone restarts; tap Turn On when it asks.

  5. The Mac installs the runner

    Nothing to tap: foundry enroll --udid <udid> --name <phone> then foundry lane up <phone> --team <team id> (the first-run tool tells your agent when). Keep the phone unlocked and plugged in.

  6. Trust the developer certificate

    The first time only: Settings › General › VPN & Device Management, your developer under Developer App, then Trust.

  7. Turn on Enable UI Automation

    Settings › Developer › Enable UI Automation. iOS will not start the Foundry runner without it.

  8. Give it internet the first time the runner starts

    Wi-Fi, or a SIM with working data. iOS checks the runner with Apple once, by itself. A phone with no internet shows Unable to Verify App. Run /usr/bin/python3 ~/.local/bin/foundry_onboard.py scan: it names this as the phone's next step.

One phone at a time

Add phones one by one. Each phone keeps its own accounts, and Foundry never moves an account between phones on its own.

Your plan sets how many iPhones can post: 1 on Solo, 8 on Fleet, 30 on Studio, or unlimited on Unlimited. Accounts on those phones are never counted.

New phone models

Settings moves between iPhone models and iOS versions: a row is renamed, sits one screen lower, or isn't there at all. So Foundry keeps one map per model and iOS version (for example iPhone14,4 on iOS 26.5), made by the first rack that plugs that model in.

When the first-run tool meets a model with no map, it maps it by itself once the phone is ready: it opens each Settings screen Foundry needs, records where every row sits and its current value, changes nothing, and uploads the map. A map holds the screen's structure only, never a screenshot, a name, an account or an Apple ID.

The models already mapped are public, so you can check yours before you buy phones:

Terminal
curl -s https://runfoundry.app/api/phonemap

A phone the rack is using answers busy and is mapped on the next run, never in the middle of a post.

Copied