Remote Deploy: run on a device

Remote Deploy exports a debug build and runs it on a selected device or through a test Web server. It is not release publishing. Availability depends on the export preset, templates, platform tools and a usable target.

Common preparation

1. Save the project and assign its main level or startup prefab.
2. Open Project → Export and create a preset for the target platform. Install matching version 1.0.0 export templates and fix preset configuration errors.
3. Enable Runnable on that preset. This belongs to a preset, not a build template. One preset per platform is selected as runnable; selecting another replaces it.
4. Prepare a device or server as described below. Open Remote Deploy on the run toolbar and choose a target. The current interface groups platform targets in one menu rather than necessarily showing a separate button for every platform.
5. Check Project Run, Output and Debugger. If CPU architecture confirmation appears, first enable the intended architecture in the preset.

The menu is hidden when platforms with runnable presets provide no targets. A preset does not guarantee SDK correctness, signing or successful installation: errors can appear after target selection.

For C#, the current export plugin implements Windows, Linux, macOS, Android and iOS. .NET Web export is not implemented; a Web menu entry does not make a C# project exportable.

Android

Configure export/android/android_sdk_path and export/android/java_sdk_path in Editor Settings, then configure the Android preset using the export guide.

Enable USB debugging, connect the device and accept its debugging authorization. Run adb devices from SDK Platform Tools: the target must have status device. For Wi-Fi, enable Wireless debugging, run adb pair IP:PORT using the pairing dialog’s address and port, then check the list again. Connection prerequisites and troubleshooting: official ADB instructions.

Select the device itself in Remote Deploy. The current Android implementation exports a temporary debug APK, installs it and launches it. export/android/one_click_deploy_clear_previous_install can remove the previous installation; leave it disabled if you need the test app’s saved data.

iOS

Remote launch on an Apple device is implemented on a macOS host. Configure Xcode, signing, bundle identifier and device pairing using the iOS guide. Suitable provisioning is required; a detected device is insufficient. Current source contains devicectl and ios-deploy launch paths. Configure the tool required by the current setup rather than installing an arbitrary replacement. This workflow was not executed by the Windows check.

Remote desktop computer

Enable ssh_remote_deploy/enabled in the target OS preset and configure ssh_remote_deploy/host and ssh_remote_deploy/port. The target needs SSH and the libraries required to run the project. Check the preset’s run/cleanup scripts, especially after editing them. Remote Deploy exports the project, transfers files over SSH/SCP and runs a command on the target computer; this differs from ordinary local editor execution.

Debugging and network filesystem

Debug → Deploy with Remote Debug adds a connection from the running project to the editor debugger. Turning it off does not prevent deployment or turn the result into a release build.

• network/debug/remote_host supplies the remote-debug address; for a direct network connection, the device must reach the editor computer through that address. Another device’s loopback does not refer to your computer.
• network/debug/remote_port is the debugger port, defaulting to 6007 in source. It is not the Web HTTP port.
• Android uses ADB reverse and localhost when export/android/use_wifi_for_remote_debug is false. This controls the debug connection route, not device discovery.
• Small Deploy with Network Filesystem omits the ordinary complete project data: the app obtains files from the editor. Disable it when testing a standalone app. The file server uses filesystem/file_server/port, not the debugger port.

Web: local server and another device

Remote Deploy offers Run in Browser and Start HTTP Server. While serving, it provides Re-export Project and Stop HTTP Server. Reloading the browser does not replace exporting project changes again.

For LAN testing, you can bind to 0.0.0.0, but other devices must open the editor computer’s IP, not 0.0.0.0 or localhost. Allow the required connection through the local firewall. SharedArrayBuffer and shared WebAssembly memory require a secure context and cross-origin isolation; TLS alone is insufficient. This concerns the relevant feature rather than every Web build unconditionally. See SharedArrayBuffer requirements.

The built-in server supplies COOP/COEP headers. With a test certificate, separately check browser trust; enabling Use TLS does not itself produce a publicly trusted certificate. For build restrictions, threads and service workers, see Web export.

Quick diagnostics

Setting types and debug-argument generation were checked in the installed editor. Menu and platform behavior were source-reviewed. Actual export, installation, ADB/SSH, Apple hardware, Web serving and a remote debugger session were not tested by this run.