Start with the step where you’re stuck
Can't see the remote screen on Windows, or is Xcode open but taking forever to build? Troubleshoot the connection, machine load and App Store workflow separately—there’s no need to reinstall everything at the first sign of trouble.
Enter a keyword to filter troubleshooting tips. Press Enter to jump to the first answer.
Can't connect
Check whether the issue is with your browser session, client credentials or local network.
Troubleshoot connection → DevelopmentBuilds are slow
Check disk space, simulators and memory pressure before considering an upgrade.
Troubleshoot performance → App deliveryApp Store workflow
Check signing, archiving, uploading and TestFlight separately.
Troubleshoot app delivery →Two ways to connect to the same Mac—troubleshoot them separately
Browser and remote desktop client issues can have different causes. If one method connects, the machine is reachable; note the error from the other method, and avoid changing your password, network and display settings all at once.
Browser session won't open, or there's no screen after connecting
First, confirm in the console that the order is paid and the instance is available to connect. Then open the session from the instance details. Don't use an old session link from your bookmarks or share the session link with anyone else.
If the console opens but the session stays on “Connecting,” reopen it, then try disabling browser extensions that might block the connection. If possible, test another network. If that fixes it, check the original network's proxy, firewall or connection restrictions.
If the screen appears but the mouse or keyboard doesn't respond, click inside the session so input goes to the remote screen. If the screen remains black, note when it started, your browser version and any error message. Don't repeatedly force-restart a machine that's building.
Remote desktop client says connection refused or authentication failed
Check the current connection address, port, username and password shown in the console. Make sure copied details have no spaces at either end. Use the remote machine's credentials, not your website login email and password.
Authentication failure and connection timeout are different issues. For authentication, check your credentials, keyboard layout and any old password saved in the client. For a timeout, check network reachability, proxy settings and instance status. If the browser connects, keep using that working route while you troubleshoot the client.
If you need an SSH tunnel, configure it with the connection details for your instance; don't copy another machine's port. Never include private keys, full passwords or session tokens in ordinary screenshots or email.
Remote screen looks too small on Windows, or shortcuts behave differently
First, match the client display size to the remote desktop resolution, then adjust scaling. If text looks blurry, avoid applying scaling in Windows, the browser and the client at the same time. If dragging the window stutters, try lowering the remote resolution and check whether interaction improves.
On macOS, common shortcuts for copying, pasting and saving use Command, not Windows Ctrl. Check the client's keyboard mapping to see which local keys send Command and Option. Mappings vary by client, so don't assume Win or Alt has a standard equivalent.
If your local system intercepts a shortcut, use the remote app's menu to perform the same action, then adjust key forwarding. If Chinese input behaves unexpectedly, check the local and remote input methods separately, and whether the client has text input forwarding enabled.
Responsive interaction and fast builds are two different things
Round-trip latency mainly affects feedback when clicking, dragging and typing; it doesn't directly indicate Xcode build speed. Start with a location close to your network, then test with your own project. For large file transfers, also consider your local upload speed and network route.
| Location | Region served | Estimated round-trip latency | Best for |
|---|---|---|---|
| Singapore | Southeast Asia | 20–50 ms | Remote desktop use, builds and project file transfers |
| Japan (Tokyo) | East Asia | 30–60 ms | Remote Mac development, builds and artifact transfers |
| South Korea (Seoul) | Northeast Asia | 30–50 ms | Remote desktop debugging, builds and code sync |
| Hong Kong | Southern China and Southeast Asia | 20–40 ms | Remote desktop use, builds and file transfers |
| US West | West Coast of North America | 25–35 ms | Remote Mac development, builds and artifact transfers |
These are estimated ranges; actual latency depends on your network. Live availability is shown in the console.
If you mainly use a remote desktop or work with simulators, prioritize interactive latency. If you only submit builds and download artifacts, a brief delay on screen is usually not the main bottleneck. Work that depends heavily on local USB peripherals isn't a good fit for remote desktop alone.
Not every slowdown comes down to the chip
A dedicated physical machine doesn't share computing resources with other customers, but your own simulators, indexing, containers and build tasks can still compete for resources. Compare the same project and similar tasks in the same environment. Don't compare a first full build directly with an incremental build.
Step 1: Is there enough disk space for the build?
Check available storage on your system and the volume where your project is stored. Xcode, multiple versions, simulator runtimes, dependency caches and Archives all use disk space. Builds also need temporary space, so having enough room for source files doesn't mean you have enough for a build.
Export any Archives or artifacts you want to keep, then remove versions and runtimes you're sure you no longer need. Don't delete your entire development directory or treat certificates, private keys or project assets as cache.
If your project runs smoothly but multiple Xcode versions and simulators are filling the disk, consider adding a 1 TB SSD. If memory pressure is the bottleneck, more storage won't replace a memory upgrade. Add-ons are priced separately from the machine; check the configuration before ordering.
Step 2: Too many simulators, or a larger project?
Open Activity Monitor and check memory pressure, CPU usage and background tasks that have been running for a while. Close unused simulators, previews and containers, then reproduce the issue with the same project. Having several runtimes installed and running several simulators at once are different issues—check them separately.
Omni M4 Desk comes with Apple Silicon M4, 16 GB unified memory and a 256 GB SSD. It's suited to building and shipping a single app. If you regularly run several development tasks in parallel and memory pressure remains high, consider Omni M4 Studio, with Apple Silicon M4, 24 GB unified memory and a 512 GB SSD.
Studio still uses the M4 chip; a memory upgrade doesn't mean every build will be faster by a fixed percentage. If you only open one simulator occasionally, try reducing background tasks before upgrading.
Step 3: Should you clear DerivedData or keep it?
If you've changed build settings, suspect a corrupted cache or see errors tied to old artifacts, stop the relevant build and locate the current project's DerivedData. Clear only that folder. Keep the error logs so you can compare what changes.
After clearing the cache, the next build may reindex, resolve dependencies and regenerate cached data, so it may take longer. Don't make clearing all caches before every build part of your routine; you'll lose the benefits of incremental builds.
If the log stalls while downloading dependencies, check access to the dependency source and your network. If it stalls at a script phase, check the script's output. Consider a machine with Apple Silicon M4 Pro only after identifying the actual build workload.
First, check whether the failure happened before or after upload
A remote Mac provides a macOS development environment; it doesn't replace developer eligibility, project signing setup or review requirements. Your source code, certificates and simulator caches are on a dedicated physical machine that isn't shared with other customers; neither the system nor the keychain is shared.
Before archiving: do the certificate and provisioning profile match the project?
Check the project's Bundle Identifier, development team, signing method and target capabilities. The provisioning profile must cover the app identifier and required capabilities. The certificate must be valid, and its matching private key must be in the keychain. Importing a certificate file alone may not be enough to sign the app.
Keep private keys and certificate backups somewhere secure that you control, and protect exported files appropriately. A dedicated machine doesn't remove the need for backups. Never send complete keys to support; when reporting an issue, share a redacted signing error, certificate type and provisioning profile status.
If your project relies on USB debugging with a physical iPhone, a remote machine can't replace connecting your own device. Remote machines work well for builds, simulator testing and distribution, but not for workflows that depend on local peripherals.
The Archive succeeded. Why did the upload fail?
First, identify which of these failed: Archive creation, artifact validation, or transfer/server-side processing. Keep the full error text from Organizer and note the stage. Don't just capture the final line saying “Failed.”
For validation issues, check signing, the app identifier, version and build number, as well as the project's required capabilities and resource configuration. If the build number is already in use, update it according to your project's versioning rules and create a new Archive. Don't keep submitting the same artifact.
If the transfer is interrupted, check your network first. If submission completes but the app record doesn't appear, check its processing status and any messages. Project configuration or review content issues require changes to the app; switching locations usually won't help.
After uploading: how can you make sure testers can access the build?
Check in order: processing is complete, the app record shows the correct version and build number, and all required compliance information is filled in. Then select a test group and testers. A completed upload doesn't mean the build is available to testers yet.
Internal testing, external testing and submitting for review are separate steps; external testing may require additional review. Confirm the group has the build you just uploaded, then ask testers to check their invitation and access status.
If upload and processing succeeded but the issue concerns tester eligibility, app content or the review result, note the relevant message first. Support can help troubleshoot the remote environment and connection; you're responsible for preparing app information and review responses.
Check your order to renew, and export files before expiry
Service is billed by the day, week, month or quarter and stops at expiry if not renewed. To avoid a long build running past the end of your rental, check the expiry time shown in the console beforehand and leave time to export artifacts and back up your project.
How do I renew? Can I retrieve files if I don't renew?
Sign in to the console and check the machine, location and expiry time in the relevant order or subscription. Then use the available renewal option to pay. After payment, confirm the order status has updated; don't assume renewal succeeded just because you closed the payment page or transferred funds from your wallet.
If you don't renew, the machine stops at expiry. Before then, export your source code, certificate backups, Archives and any build artifacts you want to keep. Don't rely on an expired remote machine to store backups.
Confirm data deletion arrangements through the console or a support ticket. This page doesn't guarantee recovery after shutdown or specify an unconfirmed retention period. A reminder being delivered doesn't replace checking the expiry time yourself.
Which payment methods are supported? What if my payment doesn't show up?
We accept USDT-TRC20 and Visa, Mastercard or Amex through Stripe. All charges are in US dollars (USD); actual payment options depend on the gateways returned by the backend.
For USDT-TRC20, check the network, address and amount requested on the payment page. For card payments, follow the gateway's verification steps. If a payment is declined, keep the message and don't retry repeatedly when the payment status is unclear.
If your payment status hasn't updated, submit your order number, payment method, payment time and transaction reference. Never send your full card number or security code. For an on-chain payment, you can provide the transaction ID; we don't need your wallet's private key.
If you need help, these four details are most useful
For an existing order, submit a support ticket through the console so we can link it to your instance and billing. For pre-sales questions, login issues or extra details, email us at support@vpsomni.com. These are our two public support channels.
- 01
Order and machine
Include your order number, machine model and location. If your email concerns multiple machines, describe each issue separately instead of just saying “my Mac.”
- 02
Time and environment
Include when the issue occurred and your time zone, your main computer's operating system, browser or client version, and the type of network you were using.
- 03
What happened and the error
Describe what you expected, what happened, the exact error and where the failure occurred. Before sharing screenshots, hide passwords, private keys, tokens and unrelated personal information.
- 04
What you've tried
List what changed after switching networks, reconnecting, closing simulators or clearing caches. Change one thing at a time where possible so the findings can be reproduced.
How we handle requests and follow up
When you submit a request, say whether you can't connect at all, a build is in progress, or a payment status is involved. This helps us assess the impact. Resolution time depends on the issue's complexity and the information needed; we don't promise a fixed response time.
Add logs and updates to your existing ticket instead of splitting the same issue across multiple requests. If you're still deciding whether to buy or rent, tell us about your project and usage. Buying may be a better fit for full-time development from one location, especially if you rely on local peripherals.
Still stuck after troubleshooting?
Include your order details, the exact error and the steps you've already tried. Haven't ordered yet? Tell us about your project needs before deciding whether to rent.