Try these checks before contacting support

Run xcode-select -p and xcodebuild -version first, and note the current developer directory and version. Once you have confirmed the target Xcode is installed, switch the developer directory to its Contents/Developer folder. The path below assumes the app is named Xcode.app. If the node uses a versioned app name, replace it with the actual path.

xcode-select -p
sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer
xcodebuild -version

A CI process may override the system selection with DEVELOPER_DIR. If the terminal and pipeline use different versions, check the job’s environment variables and the runner service user; system settings alone are not enough. If a single job needs another version, specify its developer directory in that job rather than affecting other builds on the same node.

Check disk usage before deciding whether to clear it. DerivedData may be worth addressing after toolchain changes, cache-related errors, indexing issues or low disk space. Do not assume every ordinary compile error is caused by the cache. After stopping related build tasks, renaming the cache directory so you can restore it is easier to verify than deleting it recursively.

du -sh "$HOME/Library/Developer/Xcode/DerivedData"
mv "$HOME/Library/Developer/Xcode/DerivedData" "$HOME/Library/Developer/Xcode/DerivedData.backup.$(date +%s)"

Only rename the directory if it exists; Xcode will create a new cache on the next build. Renaming does not free disk space. Once you have confirmed the new build works, delete the old cache using its actual backup path. Keep any archives you need, and do not delete Archives, project directories or signing materials along with the cache. If CI uses a custom -derivedDataPath, check that path rather than the current user’s default directory.

A signing identity requires a valid certificate and its matching private key. A certificate file on its own is usually not enough to sign a build. Import signing materials you are authorised to use with Keychain Access, then check for available identities as the user who runs the build. Do not include certificate files or import passwords in a ticket.

security find-identity -v -p codesigning
security list-keychains -d user

An identity visible to an interactive user may not be visible to the runner service user. Check the service account, Keychain search list, unlock state and access permissions. If you need to adjust Keychain access controls, authorise only the signing tools required. Do not give every app access to the private key just to clear a single error. In your ticket, provide the redacted identity check results, error code and type of user that ran the command.

Add the same environment checks to the failing job rather than running them only in an SSH terminal. Compare the user, developer directory, Xcode version, PATH and available simulators. A service process may not load an interactive shell’s configuration, so a successful manual run does not prove the service environment is the same.

whoami
xcode-select -p
xcodebuild -version
printf '%s\n' "$PATH"
xcrun simctl list devices available

If the simulator list does not include the target device, check that the required runtime is installed and the test task’s destination matches. If the runner is offline, check its service status and task logs, then review the network connection and registration details. If you do not have baseline data, validate the workflow with one build first, then increase concurrency gradually while monitoring unified memory and disk usage.

Dedicated means the physical resources are not shared with other tenants; it does not mean multiple tasks on the same node cannot affect one another. See the connection guide for full setup instructions for GitHub Actions and GitLab CI.

A wallet showing a transfer, on-chain confirmation and order verification are separate steps. Confirmation times depend on on-chain processing and payment gateway status; we do not provide a fixed number of minutes here. Check the network, recipient address and amount specified on the payment page, then confirm the transaction succeeded and check the order status in the console.

Do not send another payment just because the order has not updated yet. If you need a manual check, provide your order ID, transaction hash, transfer amount and time, including the time zone. The transaction hash is enough to locate the transfer; never send your seed phrase, wallet private key or password. If the network or amount differs from the payment instructions, keep the transaction record and explain this in your ticket.

Check the error message on the payment page and your order status first. Then confirm with your card issuer that the USD transaction is allowed and whether additional verification is required. A pending authorisation from your issuer does not necessarily mean the order has been paid; do not rely on a card notification alone to confirm delivery.

If the payment fails more than once, contact your card issuer to find out why before trying again. If the console still shows the payment as unconfirmed but your bank shows a charge, provide your order ID, payment time, amount and a redacted error message. Include the payment transaction ID if available. Never send your full card number, security code or verification text. Support will check the order and payment records; any refund or release of an authorisation must be confirmed with the gateway and card issuer.

Use the expiry time shown in the console as your reference. Check the console for the reminder send time and notification status; we do not promise a fixed number of days’ notice, and receiving a reminder should not be your only way to check whether the service is still active. We recommend adding the expiry date to your team calendar and assigning someone to confirm the renewal.

Choose a daily, weekly, monthly or quarterly term, then check that the renewal invoice matches the machine, add-ons and rental period. After payment, confirm that the order has updated instead of relying on a screenshot of the payment page. If you do not renew before expiry, node access will be affected. Back up your projects, build artifacts and essential configuration beforehand. If the time or amount in the console does not match your expectations, save the invoice number and submit a ticket before deciding whether to pay.

See the plans page for full-term pricing and storage expansion costs. For billing questions about an existing order, submit a ticket through the console. Do not include your machine password in an email.