Use SSH to run build scripts; choose remote desktop to work with Xcode’s graphical interface. UDPMac provides dedicated physical Macs. Use the connection details, account permissions and access methods shown in your console.
Already have an instance? Check its status and connection details in theConsolebefore following the steps below.
This overview shows the steps only; it does not display instance status or live connection credentials.
SSH and the graphical desktop serve different purposes. You don’t need to keep a desktop session open to run automation, or use the terminal for Xcode tasks that require visual checks.
Use it to check out projects, inspect dependencies, run xcodebuild, review logs and connect a macOS CI runner.
Use it to work in the macOS GUI, check display settings and complete tasks that require desktop interaction.
Open the project in remote desktop, check the Xcode version, project settings and signing requirements, then run a test build.
Don’t paste passwords, private keys, signing certificates or full connection details into public pages, chats or screenshots shared for troubleshooting.
Confirm in the console that your instance is ready, then check the model and node for your current order. Don’t reuse an old address from another machine.
Make sure you’re using an account authorized for this instance. If responsibilities are split across your team, check who can log in and who can change the toolchain or project files.
Check your local network and confirm the required connection ports are reachable. If the connection times out, distinguish a network issue from an authentication failure.
For SSH tasks, have a terminal client ready. For desktop tasks, use a compatible VNC client and make sure your local device allows the connection.
The host and username below are examples of command structure only. Get the actual address, account and verification details from your console.
Check the host, account and required authentication method in your console. Replace the placeholders with details for this instance; don’t reuse connection records from another instance.
When prompted for the host fingerprint on first connection, verify it against trusted instance information before proceeding. If it doesn’t match the record you checked, stop and investigate.
Check your working directory, Xcode toolchain and available disk space before running project commands. Save the required artifacts and logs, then use exit to end the session.
ssh USER@HOST.example.invalid
xcode-select -p
xcodebuild -version
exitThis example domain cannot be used to connect. Check build commands, working directories and signing settings against your own project; don’t assume this example applies as-is.
Start a desktop session only when you need graphical access. SSH and VNC may use different connection details; use the details shown for each in your console.
Once your instance is ready, find its remote desktop address, access method and account requirements in the console. Don’t copy credentials from old emails or someone else’s screenshots.
Enter the details in your local VNC client. If authentication is required, use authorized credentials. Don’t bypass connection errors by dismissing the client’s security warnings.
After connecting, adjust scaling or resolution to fit your screen. Check input focus and keyboard layout before changing project or system settings.
Save your work, close windows containing sensitive data, then disconnect in the client. Don’t save access credentials on shared devices.
A Cloud Mac provides the environment, but your project may still need changes to build successfully. Start with a small test before adding it to your regular build workflow.
After checking out or transferring the project, verify the branch, dependency files and project entry point. Note missing dependencies and setup prompts on first launch. Don’t experiment on your main branch.
Check complete: the project and expected branch are recognized.
Check the Xcode version, selected command line tools and project target settings. If the build needs signing assets, let your team manage and authorize them under its security policies. Don’t include them in logs.
Check complete: the toolchain and build target are documented.
Start with a clearly defined target. Record the failed step, key errors and artifact location. Review the output before deciding whether to fix dependencies, configuration or connectivity.
Check complete: results and redacted logs are ready for review.
When reporting an issue to your team, include the time, connection method, instance order ID and redacted error message. Don’t share full credentials or screenshots containing confidential project information.
| Issue | Check first | What to record |
|---|---|---|
| Authentication failed | Check that the account and authentication method match the instance. On first connection, verify the host identity prompt too. | Exact client error and connection method. Redact sensitive fields, including the username. |
| Connection timed out | Check the instance status, local network, destination address and required connection ports. Distinguish a timeout from an incorrect password. | Time, selected node, network environment and the step where the timeout occurred. |
| Display lag | Check local network stability and try reducing the remote desktop’s display load. See whether terminal tasks are affected too. | Time, client display settings and steps to reproduce the issue. |
| Session disconnected | Check for local network changes, client alerts and instance status. Before reconnecting, confirm there are no unfinished file operations. | Last action before the disconnect, client alert and result of reconnecting. |
After ending your SSH or remote desktop session, review accounts, work files and future access. Before your rental ends, export any project data and build artifacts your team needs to keep.
Check for active sessions or temporary access that are no longer needed, and handle them according to your team’s process.
Confirm your artifacts are archived. Before deleting temporary files, check that they won’t affect the next build.
Remove saved connection details from shared devices. Don’t leave private keys, signing assets or logs with sensitive information in public locations.
To learn how we handle site and service information, read ourPrivacy Policy.
Check the model, rental term and node first. Once your Mac is ready, get the connection details from your console and follow this guide to connect over SSH or remote desktop.