Start by checking the model and physical node in your order, then move on to desktop access, your development toolchain, or build tasks. These guides provide a checklist; use the delivery details shown in your console for connection settings and current availability.
Confirm your model, billing period, and selected add-ons.
Match the physical node to your order and delivery details.
Set up your remote desktop client using the method provided.
This checklist doesn’t show connection addresses or credentials. Sign in to view your delivery details.
Search by keyword or choose a topic. Results link to the relevant checks on this page, so there’s no need to guess connection ports, tool versions, or prices.
12 guides
No matching guides. Try “connection,” “certificates,” “runner,” or “billing period,” or clear your search to see all steps.
You’re connecting to a dedicated physical Mac, not a virtual machine where generic image settings can be assumed to apply. Match your order to the delivery details before configuring your client.
In the console, confirm the model, daily, weekly, monthly, or quarterly billing period, and any add-ons. If the order doesn’t match your expectations, review your selections rather than inferring hardware or cost from the model name.
Match the node in your delivery details to your order. Available locations include Singapore, Tokyo, Seoul, Hong Kong, and the US West Coast. Check the console for real-time availability.
Make sure your local network is stable, and have a remote desktop client compatible with the connection method provided. After signing in, check the connection details. Don’t include addresses or credentials in public posts.
First, make sure your local network can reach the required services. Then check that your client settings match the delivery details. If you can see the screen but can’t interact with it, note what happens with the display, keyboard, and mouse separately. Don’t change connection settings without checking them first.
Note the selected node, client type, time the issue occurred, what you saw on screen, and the steps you’ve tried. Sign in to the console to submit a support ticket. For the full connection walkthrough, see the remote desktop guide.
Read the remote desktop guideMake a checklist before recreating your environment. Don’t assume every tool, plugin, or specific version your project needs is already installed; check the actual machine and project documentation.
Note the required macOS and Xcode versions, SDKs, and command-line tools. After connecting, check the installed versions and decide whether to adjust your toolchain. Start with a minimal build to verify everything works.
Check against: project settings, team build docs, installed versions.
List package managers, lockfiles, runtime versions, and environment variable names. Install dependencies on the cloud Mac and run tests one by one. Don’t copy local settings wholesale: they may contain tokens, private keys, or personal paths.
Check against: dependency lockfiles, environment docs, test output.
Check your signing identity, provisioning profiles, project target settings, and team access permissions separately. Transfer signing assets only through a team-approved secure method. After verification, check where temporary files are stored.
Check against: project signing settings, asset validity, access permissions.
After each group of dependencies, run the relevant build or test command and save any error messages. This makes it easier to find the cause of a problem than migrating everything at once and troubleshooting afterward.
Before adding a self-hosted runner, decide who can trigger jobs, what those jobs can access, and where to find logs if a build fails. A successful interactive desktop build doesn’t mean an automated job has the same permissions.
Check which account registers the runner, its repository or project access, and the conditions that trigger jobs. Keep the permissions for your everyday remote desktop account separate from those needed for automated jobs. Don’t broaden access just to troubleshoot.
Check Xcode, command-line tools, project dependencies, and the working directory. Start with a reproducible minimal job. Check its exit status, build logs, and artifact path before connecting the full pipeline.
Identify the credentials and certificates each job needs, and restrict access to them. Don’t put them in your repository, script output, or support tickets. After the job finishes, check temporary artifacts and logs for accidentally exposed secrets.
If a manual desktop build and a runner build produce different results, compare the account, working directory, tool versions, and environment variables first. Keep the error logs from both builds and rule out differences one by one.
Check the model, node, billing period, and add-ons, then review the final charges. Don’t compare prices from different billing periods as if they were the same daily rate.
Daily, weekly, monthly, and quarterly are four distinct order periods. When you switch periods, check the price for your model and selected add-ons, along with the actual start and end dates in your order.
If you select an extra +1TB SSD, +2TB SSD, or Thunderbolt 5 daisy chaining, check that each item is selected and review its price for the chosen billing period. Unselected items aren’t part of your order.
Pay with USDT-TRC20 or Visa, Mastercard, or Amex processed by Stripe. All charges are in USD. Check the console at checkout for the payment options currently available.
Use these terms to distinguish the machine, location, connection method, and billing unit when reviewing delivery details or describing an issue.
These are suggested learning topics, not a list of published articles. For steps you can follow now, use the guide index above.
Understand the difference between architecture concepts and how a dedicated physical Mac is delivered.
From runner permissions and your first build to checking logs and artifacts.
Plan how signing assets are transferred between remote development and automated jobs.
Separate build checks on your cloud Mac from the submission steps that follow.
Include dependencies, signing, build settings, and artifact verification in your workflow.
Start with a tool inventory, then recreate versions and project dependencies one by one.
Include your model, selected node, when the issue occurred, expected and actual results, and steps you’ve already tried. For build issues, attach error logs with sensitive information removed. Never send passwords, tokens, or private keys through public pages, email, or support tickets.
Review your options before placing an order. For connection or billing questions about an existing order, sign in to the console.