Order & device
Confirm the Mac, model and instance ID linked to your order. If you manage multiple devices, identify the one you need first to avoid transferring project files to the wrong machine.
Connection & Build Support
Start with your order details. Connect to your cloud Mac.
Confirm your device, region and access permissions before connecting over SSH and checking your build environment. Use this checklist for first-time setup or troubleshooting. Your connection address, username and key are specific to your order.
Already placed an order? Open it in the console, then follow the checklist on the right.
Connection checklist
01 / 03
Check first, then connect
One order, one device.
- Device
- Check the model and instance ID in your order
- Region
- Confirm your selected region and connection route
- Access
- Use the connection details provided for this order
Public examples contain no real addresses, private keys or access tokens. Use the details shown in your console.
Before you begin
Check your connection details before opening a terminal.
Find each detail in your order instead of copying connection information from old notes or chats, where it may have changed. If you haven't ordered yet, visit the Models & Pricingpage to check available configurations and rental terms.
Region & connection details
Confirm the region selected for your order, then find the connection address, port and username in the device details. Don't use the example address on this page to connect.
Account & access
Check that your current account can view the order and its connection details. Keep your private key in a secure local environment; never share it in support tickets, repositories or public pages.
Never share sensitive credentials.When troubleshooting, you can share redacted error messages, but never send private keys, complete tokens, certificate contents or unredacted logs containing personal information.
Connection steps
Connect securely in three steps.
Get the actual parameters for your order before preparing your local key and verifying the host identity for the first time. Network connectivity, account authorization and host identity are separate checks—don't skip verification just because you see a login prompt.
-
01
Find your connection details
Sign in to the console, open the relevant order and note the address, port, username and connection instructions for that device. If the details aren't available yet, check the order status rather than guessing the address.
-
02
Set up your SSH key
Check the permissions on your local private key file and add the corresponding public key as instructed in your order. Use separate, restricted credentials for CI; don't copy your personal development machine's private key into a build repository.
-
03
Verify the host identity
On your first connection, verify the host fingerprint against trusted device details. If it doesn't match or changes unexpectedly, stop and check that you selected the right device, address and connection route. Don't ignore the warning.
Command examples
After connecting, run a few basic checks.
The output below illustrates the order of checks. It doesn't reflect any device's actual OS version, build result or project setup. The example address 192.0.2.10 isn't your order's connection address. Replace it with the details from your console before running the command.
First confirm you can access the right device, then check which Xcode command-line tools are selected, and finally run your build task from the project directory. Troubleshoot each step on its own; there's no need to move your entire CI pipeline over at once.
Connection & build checks · Example
$ ssh -i ~/.ssh/id_ed25519 operator@192.0.2.10
Example output: Connected to the target device; verify the host identity
$ xcodebuild -version
Example output: Shows the Xcode version currently installed on the device
$ fastlane build
Example output: Checks the project configuration and returns the build resultExample commands contain no real credentials. fastlane build only works if the project defines a matching task. Use the command specified by your project configuration.
First build
Record versions and dependencies before comparing build results.
A successful connection only confirms that you can access the device—it doesn't mean the development environment matches your project. Complete these checks before setting up a Runner or uploading large batches of project files. Actual OS and tool versions depend on the device you rent.
macOS & Xcode
Note the macOS version, the installed Xcode version and the developer directory returned by xcode-select -p . If your project requires a specific SDK, check which versions are available before building.
Check: OS version, Xcode version and command-line tools path.
Project dependencies
Install dependencies from the repository's lockfile. Check the package manager, scripting runtime and plugins required by your project. Manage tool installation, project configuration and signing materials separately; a single failed build doesn't necessarily indicate a device issue.
Check: lockfile, installation logs and dependency versions.
Minimal build
Run a reproducible check or build command from the project directory and save the command, exit status and first error location. Once the build works locally, connect the same task to CI.
Check: working directory, full command and first failing step.
CI/CD setup
Have your Runner reproduce a verified manual build.
The goal of CI/CD setup is to make a successful build repeatable by recording its commands, dependencies and permission requirements—not to switch to an environment you can't trace. Registration and executor settings depend on your CI system. Never paste real registration tokens into public configuration.
A
Registration & isolation
Register a Runner for the target device in your CI system and verify that it receives the intended projects and jobs. Check the execution user, working directory and concurrent job settings.
B
Keys & signing materials
Store access keys and signing materials in your CI system's secure secrets store. Don't put them in repositories, build script output or caches. Grant only the permissions each job needs.
C
Caches & artifacts
Specify dependency cache paths and cleanup rules, and save build artifacts to your team's designated location. If an error can't be reproduced, run a comparison build without the old cache.
D
End the session
When a job finishes, check for temporary files, background processes and active sessions. When handing off a device or changing permissions, revoke unneeded access and make sure no credentials remain in the working directory.
Troubleshooting
Start with the first step that failed.
Note where the issue occurred, then save the relevant command, exit status and redacted logs. Don't send only a screenshot of the final “failed” screen: the first error is usually more useful than the last summary line.
SSH connection failed
Confirm the order and target device, then check the address, port and whether your local network can reach it. Next, check the username, key permissions and host identity prompt. Record timeouts separately from permission errors: check the connection route for the former and authorization for the latter.
Signing configuration issue
Check that the signing configuration and build target match the CI execution user. Don't paste certificate or private key contents into a support request; share the redacted error line and the build step that triggered it.
Build failed
Compare the Xcode path, dependency versions, working directory and environment variable sources used locally and in the CI job. Find the first actual compiler or script error before deciding whether to clear the cache and run again.
Not enough disk space
Check available space and distinguish project files, build artifacts, dependency caches and temporary files. Confirm who owns each file before removing it. If your workload consistently needs more capacity, visit the Planspage to check storage add-ons.
When submitting a support request: Include the device model and region for your order, when the issue occurred, the command you ran, the first error location and the steps you've tried. Remove tokens, certificates, private keys and personal information before sending.
Get support
Still stuck after troubleshooting? Include your order details.
For an existing order, sign in to the console, check the device details and submit a support ticket linked to the order. For pre-sales questions or help choosing a plan, see the email checklist on our contact page. Never include your account password or complete keys in a support request.
Ready to get started?
Choose your device, then follow the setup checklist.
Choose from three tiers of dedicated Apple Silicon physical machines, with daily, weekly, monthly and quarterly rental options. Check the model and rental term, then get your connection details in the console after ordering.