Closed fahall closed 2 years ago
Looks like Unity Hub v3.0.0 was released yesterday. Perhaps that's the cause: https://unity3d.com/hub/whats-new
I've added possible solution here https://github.com/kuler90/setup-unity/pull/7
Hi all, I have investigated the problem. Looks like now Unity Hub CLI commands may execute successfully, but with bad return code. The same problem was fixed for Windows earlier. I have released a new version with the fix for macOS.
My builds were working just fine until about 2 days ago when they suddenly started failing. I reran a build that succeeded 2 days ago and it now fails (no changes to the code, I literally reran the same workflow). The Unity Setup step fails with Unity Hub Exit Code of null, but the log looks like unity-hub was successful 🤷 .
I've attached logs in case they're helpful.
It doesn't look like anything changed with the Github Action, so I suspect something changed either on the UnityHub end or in the action runners, but I'm at a loss of how to proceed in debugging this.
Any suggestions?
1_Set up job.txt 2_Checkout Repository.txt 3_Cache Unity Library.txt 4_Set Development Version.txt 8_Set Default Build Number.txt 10_Set Default Build Path.txt 11_Create Build Manifest.txt 12_Setup Unity.txt 36_Post Checkout Repository.txt 37_Complete job.txt