Unity Hub exit codes incorrect

Hi there,

I'm having a problem trying to run the Unity Hub in an automated and headless fashion. Many commands are returning non-zero exit codes where they appear to succeed.

This means that I cannot assert against command failures in my scripts and must parse the standard out to try and determine whether the command succeeded or not. This is less than ideal.

For example (ran in Git Bash):

Code (CSharp):

1.  
2. ❯ /c/Program\ Files/Unity\ Hub/Unity\ Hub.exe -- --headless install-path --set "E:/Unity"
3.  
4. (node:22344) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
5. All Unity Editors will be installed to E:/Unity
6.  

This command appears to succeed (ignoring the deprecation warning), but if I check the exit code (echo $?), the exit code is 1.

I've observed this happening for installing Unity versions over the CLI too:

Code (CSharp):

1. /c/Program\ Files/Unity\ Hub/Unity\ Hub.exe -- --headless install --version 2019.3.7f1 --changeset
2. 6437fd74d35d

displays the same behaviour.

I'm using Unity Hub version 2.3.0.

 

Hey Jamie

I too see this in uses of the CLI arguments for the Unity Hub on the saem version as well. Have you had any luck with it up to this point:

@bradunity would you be able to see if this is something the Hub team are aware of or could investigate?

 

Same problem here using latest version 2.4.2...

 

This has been a problem for a long time. I was told that is was the correct behaviour and the bug issue was closed.

 

I think it's more, "this is the mess we've made and you have to live with it."

 

https://issuetracker.unity3d.com/is...e-is-set-to-1-when-executing-hub-cli-commands

 

Resolved as "By Design"

Unity being Unity...

 

Yeah this is bonkers - if it's by design, then what's the intended way to tell whether a Unity Hub CLI command succeeded or not?