An update failed or Udon did not reconnect

Udon checks for releases at startup, about hourly, and after wake or restored connectivity when a check is due. An admin chooses when to install. Running containers stay with their engine while Udon restarts; dashboard terminal sessions end.

The update check fails or shows an unexpected versionCopy Anchor Link

Open Settings → License and, in the About card, click the circular-arrow button (Check for updates now). When a release is ready, Update takes its place. The Mac running Udon needs an internet connection. If a check fails, a previously found update can remain visible. Restore connectivity and check again before retrying an installation.

Udon offers the build assigned to your Mac. Dev-enrolled Macs receive private Beta builds; other Macs receive Stable. An assignment can offer an older version, for example when returning from Beta to Stable. Udon has no local channel switch. If the assignment looks wrong, contact support with the Mac's serial and the running and offered versions.

Dev enrollment allows normal updates. If About instead says Udon is running in dev mode. Updates are disabled., you are running a local developer build. Use a signed installed release for updater testing.

The download or validation failsCopy Anchor Link

Keep the exact error. Before replacing files, Udon checks the release signature, archive paths, size, checksum, app signature, architecture, and matching components. A failed download leaves the current installation in place. Retry after restoring connectivity or freeing the disk space named in the error. Use the official installer or update controls for the next attempt.

The dashboard stays disconnectedCopy Anchor Link

Keep the dashboard open while Udon restarts and checks the replacement. Management changes pause during replacement and validation. If the new version needs a new helper, the Welcome to Udon window opens on the Mac; click Allow and approve the administrator prompt. If a permission screen appears, follow Verify Full Disk Access. A pending grant doesn't fail the update: Udon completes it and keeps asking for the grant.

The dashboard follows the operation for up to 10 minutes. A timeout reports that Udon has not returned; it does not prove the installation finished or failed. Check the Mac's connection and open Udon from its menu bar. After a Mac reboot, sign in to the owning macOS account so its background services and recovery process can resume.

When the dashboard is reachable, sign in and open /api/updates at the same address. Its operation reports an id, target build, phase, and any error. succeeded confirms the replacement; rolledBack means the previous installation was restored. Keep the operation ID and error if you need support. For startup or address errors, follow Udon won’t start or finish setup.

Udon restored the previous version or needs recoveryCopy Anchor Link

Udon retains the previous app, dashboard, service files, and a consistent database backup until the replacement passes its checks. If startup fails, a separate recovery process restores them. After a reported rollback, confirm the running version in Settings → License → About.

If recovery failed and Restore previous installation appears in the update dialog or About card, an admin can choose it to retry. If the dashboard is unavailable and a failed recovery has retained its files, run this in Terminal from the owning macOS account:

udond recover-update --retry

The command asks the recovery service to retry; confirm its result after Udon returns. Keep the state folder, transaction record, and retained backup files. Let an active update or recovery finish before running another installer or uninstaller. If recovery still fails, send [email protected] the operation error and relevant udond.log lines, with private information removed.