A package install or update appears stuck
Check Homebrew availability, answer terminal prompts, and verify a package action before retrying it.
An install or update can pause for a download, a build, a confirmation, or a macOS password. Read the last lines in the package dialog before starting another attempt. Homebrew packages run directly on the Mac, independently of the selected container engine.
Check whether Homebrew or the package list failed
If Packages says Homebrew is not installed, follow the Packages setup instructions on the Udon Mac. Udon looks for Homebrew only when it starts, so afterwards choose Restart Udon under More in the menu bar panel and reload the page. “Could not read installed packages” means Homebrew was found but its package query failed.
On the Mac, use Terminal under the account that runs Udon to check:
brew --version
brew info --json=v2 --installedKeep any error printed by the second command. If both commands work but the page still fails, restart Udon as above, reload Packages, and keep Udon's displayed error for support.
Check your account and the action
Installing, upgrading, and removing packages require a Udon admin account. Ask an existing admin to perform the action or check your role. New installs start from the App Store's Homebrew tab; the Packages page manages installed items.
If the dialog opens and immediately ends, read its output. “Could not start the package action” means no usable command was started. An exit code identifies a command that ran and failed.
Answer the live terminal
Click inside the output area to type. Answer a confirmation only after reading it. A sudo
prompt needs the relevant macOS account's password; it does not use your Udon password.
Password entry may show no characters. Press Enter after typing it.
If output continues, leave the action running. To interrupt an action deliberately, send Ctrl-C in the terminal. Closing the dialog with × or Escape does not stop the command. The Close button stays unavailable until the connection closes, then becomes Done.
Confirm the outcome before retrying
For a single command, “Finished” reports a successful exit. “Exited with code…” or “Stopped” reports failure or interruption. A mixed formula-and-cask update can run several commands; read each one's output and check every selected package afterward.
Done also becomes available after a lost connection, so it alone does not confirm success. The command keeps running on the Mac after the dialog closes or the browser disconnects. Reload Packages and check the installed version or removal. If the result is still unclear, check for a running Homebrew process on the Mac before starting the same action again.
The action is complete when Packages shows the expected installed version, or the removed package no longer appears. Clear the package filter before checking a missing row.
If it still fails, email [email protected] with the package name, whether it is a formula or cask, the action, Udon and Homebrew versions, and terminal output around the failure. Mention any lost connection or unanswered prompt. Exclude passwords.