Running on Windows 10 + powershell with choco.
When running spatial setup install-dependencies, it might sometimes try to install an older version of a package (like it happened to me with Unity). Therefore, the command returns with an error and suggests using either --force or --allow-downgrade.
–force doesn’t work for me. I had Unity installed without chocolatey, and it was a newer version than the one associated to SpatialOS version 10.4.1, so that might be it. It would be nice if that didn’t matter.
–allow-downgrade seems no longer available, I get “invalid flag” errors and I can’t see it listed when running spatial setup help. If it’s no longer available, it would be nice if the error message didn’t suggest it.
I had to manually choco uninstall unity and all of its dependencies one by one and then spatial setup install-dependencies worked fine, but it would be great if these issues were handled a bit more gracefully.