Choose connection, Xcode, CI/CD, storage, networking, or renewal to keep the relevant entry points. You can also search by command, symptom, or tool name.
Showing all 6 help categories.
Try a shorter keyword, or clear the category and search for a command name. For questions about an existing order, submit a console ticket directly.
Use the connection details shown on the instance details page in the console. Do not guess the host address from an old ticket or historical command; copy the current details again after a node is re-provisioned.
Open the instance details in the console and copy the host address, SSH username, port, and key information. Confirm that the selected order and node match, then paste the command into your local terminal.
Store the key file in a directory controlled by your local user. Do not commit it to a Git repository, build artifact, or team chat. The filename is up to you, but the path in subsequent commands must match.
Run this in a local macOS or Linux terminal: chmod 600 ~/.ssh/oncemac_key. If SSH reports that the private-key permissions are too open, fix the permissions first instead of bypassing the security check.
Run the SSH command provided by the console. On the first connection, verify the source of the host fingerprint. After entering the node, run hostname, sw_vers and whoami to confirm the host, operating system, and current user.
Change only one variable per investigation. First confirm that the SSH session is stable, then check the Xcode version, and finally run the build command with a result bundle and logs. This separates connection, toolchain, and project issues.
$ ssh -i ~/.ssh/oncemac_key user@host
Last login: current session
connected: once-node
$ xcodebuild -version
Xcode 16.x
Build version 16x
$ xcode-select -p
/Applications/Xcode.app/Contents/Developer
$ set -o pipefail
$ xcodebuild \
-workspace App.xcworkspace \
-scheme App \
-destination 'generic/platform=iOS' \
-resultBundlePath ./BuildResults.xcresult \
build | tee build.log
** BUILD SUCCEEDED **
$ bundle exec fastlane ios build
[fastlane] resolving dependencies
[fastlane] archive completed
[fastlane] lane finished successfully“It builds locally but not on the node” is rarely enough to identify the cause. Compare both environments using the same commit, dependency lockfile, scheme, destination, and environment variables, then compare their outputs.
Run xcodebuild -version, and record the major version and Build version. If the pipeline requires a specific version, print it at the start of the job instead of checking only during initial setup.
xcodebuild -version
xcrun --find simctl
swift --versionRun xcode-select -p to check the current Command Line Tools path. If multiple Xcode versions are installed, define DEVELOPER_DIR explicitly in the runner environment so interactive sessions and automated jobs do not read different paths.
xcode-select -p
echo "$DEVELOPER_DIR"
xcrun --sdk iphoneos --show-sdk-pathFirst confirm that the keychain is accessible and that the certificate name matches the provisioning-profile requirements. Then check the project’s Team, Bundle Identifier, and signing method. For a ticket, provide only the redacted error section—never attach certificates, private keys, or passwords.
security list-keychains
security find-identity -v -p codesigning
xcodebuild -showBuildSettingsUse set -o pipefail to preserve the real exit status, while using tee to write the log. For complex failures, generate .xcresult and remove usernames, paths, tokens, and business data before sharing.
set -o pipefail
xcodebuild build | tee build.log
echo "${PIPESTATUS[0]}"OnceMac provides dedicated physical nodes with a complete macOS command-line environment. Teams should validate platform features, plugin compatibility, and job definitions against their own repository and version requirements.
runs-on condition in the workflow.whoami, pwd, the Xcode version, and available disk space at the start of the job.Rebuild the toolchain from Git, lockfiles, and Brewfile whenever possible, and migrate only the working directories and caches you actually need. Copying an entire legacy user environment also brings outdated settings, absolute paths, and sensitive credentials to the new node.
Use dry-run mode first to review what will be copied and deleted, then perform the actual sync. The operator must confirm any deletions at the destination.
rsync -avhn \
--exclude '.git' \
--exclude 'DerivedData' \
./Project/ user@host:~/Project/Record the branch, commit hash, and uncommitted changes on the source node. After cloning on the new node, verify the hash before restoring dependencies; do not use an archive instead of version history.
git status --short
git rev-parse HEAD
git clone repository-url
git checkout commit-hashReview the list before exporting and remove software you no longer need. After restoration, verify each command’s version; a successful install command alone does not prove that the environment works.
brew bundle dump --file Brewfile
brew bundle check --file Brewfile
brew bundle install --file BrewfileSSH private keys, repository tokens, signing material, environment files, and service keys should not be copied in bulk with the project directory. After confirming least-privilege access on the new node, configure them again through your team’s approved secure process.
Handle all five issue types in this order: confirm the symptom, run the minimum command, record the result, and stop ineffective changes. Expand an item to view its checklist.
chmod 600 to check local private-key permissions and confirm that the key path in the command exists.ssh -vvv to inspect the connection phase, but remove personal information from the full address, username, and key path before submitting a ticket.set -o pipefail to preserve the real exit code, and export .xcresult or the complete log.df -h to view volume capacity, then use du -sh to locate the workspace, DerivedData, archives, and dependency caches.uptime and compare the boot time with the time the issue occurred.Submit questions about existing orders, node status, and renewals through a console ticket first. For configuration and scope questions before ordering, email us. The only public contact email is support@oncemac.com.
Provide the order number, configuration name, and node region. Do not provide payment credentials or complete billing details.
Specify the time zone, first occurrence, most recent reproduction, and whether the issue is ongoing.
List the command, expected result, actual result, and exit code. Avoid writing only “it doesn’t work.”
Keep the error context, but remove keys, tokens, passwords, full IP addresses, signing material, and business data.
Describe the network, version, path, disk, and retry checks completed to avoid repeating ineffective steps.
For node connection, build, billing, renewal, and order-status issues. The ticket is linked to your signed-in account to preserve the instance context.
Open the consoleInclude your use case, target node, Xcode version, concurrent build count, storage requirements, and desired activation time.
support@oncemac.comOnceMac offers 3 available configurations across 6 nodes, operating normally 365 days a year. All orders are billed in USD, with orders, nodes, and tickets managed centrally in the console.