eas simulator:start supports local egress

Introduced 2026-09-10 · score 0.97

HOW TO USE IT

When an iOS simulator session needs access to a development server on the CLI machine or its network, start it with `--egress local` and repeat `--egress-allow <host:port>` for each destination. Use `localhost:<port>` or `127.0.0.1:<port>` for loopback; the egress client must stay running for the session.

WHY THIS HELPS

When an iOS simulator session needs to reach a development server on the CLI machine or its network, start the session with local egress and allow the server host and port.

REQUIREMENTS AND LIMITATIONS

• Version: v24.1.0
• --egress local (required): Select local egress; the client must remain running for the session.
• --egress-allow <host:port> (required): Exact destination on the CLI machine or its network that the simulator may access through local egress; repeat for multiple destinations. Requires `--egress local`. `localhost` or `127.0.0.1` forwards that port from the simulator host to the CLI machine.
• --config-type dotenv|env: For `simulator:egress`, read session credentials from `.env.eas-simulator` (`dotenv`, default) or the current shell environment (`env`).
• --platform ios: Select iOS as the simulator platform.
• Prerequisite: Keep the local egress client running for the life of the session.
• Prerequisite: `--egress-allow` requires `--egress local`.
• Prerequisite: The v24.1.0 release documents the iOS system proxy and local egress behavior.
• Requests exit from the CLI machine only when they honor the device host's system proxy.

FIRST-PARTY EVIDENCE

• https://github.com/expo/eas-cli/releases/tag/v24.1.0
• https://github.com/expo/eas-cli/blob/main/packages/eas-cli/README.md
• https://github.com/expo/eas-cli/blob/v24.1.0/packages/eas-cli/src/commands/simulator/egress.ts

Check the installed version and the source before using it. Entry JSON

Report a problem with this card