Troubleshooting Guide

Extension not visible

Check PowerToys, Command Palette, package install, manifest registration, CLSID consistency.

Stale package or PowerToys needs reload / restart.

Local debug: rebuild with -p:Platform=x64, re-register with Add-AppxPackage -Register, restart PowerToys.

Release validation: remove old version first:

Get-AppxPackage *CommandPalette-Unity* | Remove-AppxPackage

Install produced bundle:

Add-AppxPackage -Path "AppPackages\UnityExtension_*\UnityExtension_*.msixbundle"

If stale after install, reload Command Palette or restart PowerToys.

Wrong process, stale output, or code paths not executing.

ProjectParser may swallow exceptions. Confirm %APPDATA%\UnityHub\projects-v1.json exists + valid JSON.

Check Unity Editor path resolution + registry lookup.

Recheck restore, trim / AOT warnings, packaging, manifest behavior.

Known non-fatal warnings:

IL2081 / IL2104 from CsWinRT / Windows SDK projection code safe to ignore if package installs + runs.
mspdbcmf.exe could not be found means symbols package not generated; app bundle still valid.
Local publish commands suppress trim warnings by default; use -p:SuppressSdkNoise=false to inspect.

If dotnet-outdated.exe suggests newer Microsoft.WindowsAppSDK, treat as compatibility check, not automatic upgrade.

If Release packaging fails with WindowsPackageType=None + GenerateAppxPackageOnBuild=true, remove hard None for build path.

If packaging fails with IL2104 / NETSDK1144, check trimming enabled for packaging build path, temporarily disable if needed.