Run the visionOS Simulator on a Rented Mac

Direct recommendation: request a Figment M-series Mac from $95/month to run the visionOS Simulator. Apple requires a Mac with Apple silicon for the visionOS Simulator, so the $29 virtual Intel macOS plan and any Intel Mac cannot run it. The M-series plan is request-based; the specific chip, RAM and disk are confirmed in your quote. Start the request at /mac-hosting/start.

Why visionOS Simulator Needs Apple Silicon

Apple's Developer Technical Support staff state plainly that "visionOS Simulator is not supported on Intel based Mac hardware," referencing the Xcode 15 Beta 7 release notes in the Apple developer forum thread 735675. The Xcode release notes themselves are the canonical source — see the Xcode 15 release notes. This is a runtime limit on the simulator itself; cross-compilation does not unlock it.

Figment's $29 virtual Intel macOS plan runs real macOS on Linux/KVM without GPU acceleration or audio. It can host compatible Intel-supported Xcode toolchains (Xcode 26 or earlier) for Intel-friendly targets, including cross-compiling arm64 device builds, but it cannot execute the visionOS Simulator. For visionOS work you need the Apple-silicon class: Figment's M-series Mac from $95/month. The $49 i3 and physical M-series tiers are also available by request while supply is confirmed.

Pick the Right Figment Plan for visionOS Work

If you only need a single Apple silicon rental and a shell, compare 12 × $95 = $1,140 to CloudMac's $999/year advertised M4/16 GB tier (effective $83.25/mo, $141 cheaper per year than Figment's entry M-series). Figment's $95 entry is not pinned to a specific M4 configuration; if a specific M4/16 GB/256 GB plus admin access is all you need, CloudMac's listed price is lower. Figment's differentiator is the Managed Build / Team tier: the CI setup, backups, monitoring, and monthly support hours are the paid work, not just the hardware.

Install the visionOS Simulator Runtime

The visionOS runtime ships as an optional download. Install it once on the rented Mac, through the Xcode UI over VNC or from a terminal.

# List already-installed runtimes
xcrun simctl list runtimes

# Download the current visionOS runtime (Xcode 15+)
xcodebuild -downloadPlatform visionOS

# Confirm the runtime appears (visionOS shows up as xrOS)
xcrun simctl list runtimes | grep -i xrOS

The runtime identifier printed by simctl list runtimes is the exact string to use below (for example com.apple.CoreSimulator.SimRuntime.xrOS-2-0). Version strings differ across Xcode releases; always copy the identifier your installation prints rather than hard-coding one.

Create, Boot, and Launch Your App

This is an unexecuted example to adapt to your project. Run it on the rented Mac in the browser console or over VNC, replacing the scheme and workspace with your own.

set -euo pipefail

# 1. Pick the Apple Vision Pro device type
DEVICE_TYPE=$(xcrun simctl list devicetypes | \
  awk -F'[()]' '/Apple Vision Pro/ {print $2; exit}')
echo "Device type: $DEVICE_TYPE"

# 2. Pick the installed visionOS runtime
RUNTIME=$(xcrun simctl list runtimes | \
  awk -F'[()]' '/xrOS/ {print $2}' | tail -1)
echo "Runtime: $RUNTIME"

# 3. Create and boot the simulator
UDID=$(xcrun simctl create "Vision Pro Dev" "$DEVICE_TYPE" "$RUNTIME")
xcrun simctl bootstatus "$UDID" -b

# 4. Build for the visionOS Simulator (use YOUR scheme/workspace)
xcodebuild build \
  -workspace YourApp.xcworkspace \
  -scheme YourAppScheme \
  -destination "platform=visionOS Simulator,id=$UDID" \
  -derivedDataPath ./DerivedData

# 5. Locate the built .app, install, launch
APP_PATH=$(find ./DerivedData/Build/Products -type d -name "*.app" \
  -path "*visionOS*" | head -1)
BUNDLE_ID=$(/usr/libexec/PlistBuddy -c "Print :CFBundleIdentifier" \
  "$APP_PATH/Info.plist")

xcrun simctl install "$UDID" "$APP_PATH"
xcrun simctl launch "$UDID" "$BUNDLE_ID"

# 6. Stream app logs from the booted simulator
xcrun simctl spawn "$UDID" log stream --predicate "process == \"$BUNDLE_ID\""

The set -euo pipefail line makes the script stop at the first failure, so a broken build cannot look like a successful run. Use your real Xcode scheme name — there is no safe default.

Debug the Running App over Screen Sharing

Connect to the rented Mac using Figment's browser console or your own VNC client, then work normally:

• Simulator window — the shared space renders as a 2D window; dragging and clicking inside substitutes for head and hand input.
• View Debugger — in Xcode, Debug → View Debugging → Capture View Hierarchy inspects RealityKit entities and SwiftUI layout.
• Reality Composer Pro — open .reality and USDZ scenes for visual editing on the rented Mac.
• Logs without Xcode — the simctl spawn … log stream command above tails app logs to the terminal.

Network latency between you and the Mac only affects the pixels on your screen. The simulator, physics, and timeline run on the rented Apple silicon Mac itself, so test results do not depend on your local connection speed.

Common Errors and Quick Fixes

Renting the Mac turns the Apple silicon prerequisite into a monthly line item. Request a configuration at /mac-hosting/start and tell us the Xcode version, disk, and whether you want the Managed Build tier to handle CI and backups.

Related guides:

• Build a Multiplatform Xcode Project Remotely
• Mac Team Onboarding with Remote Xcode
• Mac GitHub Actions Self-Hosted Runner