Bug description
I built and installed game-ci CLI from source because of #272 .
It works to run game-ci --help.
But trying to build my project fails:
game-ci build "./UltraStar Play" --target-platform StandaloneOSX
...
[ERROR] Error: Unity Hub is not installed at the default location.
Please install Unity Hub at the default location and try again.
at setup (/$bunfs/root/game-ci:227561:24)
at setup (/$bunfs/root/game-ci:227689:29)
at execute (/$bunfs/root/game-ci:228681:30)
at run (/$bunfs/root/game-ci:230086:44)
at processTicksAndRejections (native:7:39)
But, Unity Hub is installed in the default location. I did not change anything.
ls -d "/Applications/Unity Hub.app"
/Applications/Unity Hub.app
How to reproduce
Try to build a project on macOS with latest version.
The Unity project builds.
Additional details
AI says, the expected path contains a literal double-quote, which is why the actually correct path is not recognized.
Not sure if this is true, but the variable declaration does look suspicious to me.
See setup-mac.ts
class SetupMac {
static unityHubBasePath = `/Applications/"Unity Hub.app"`;
static unityHubExecPath = `${SetupMac.unityHubBasePath}/Contents/MacOS/"Unity Hub"`;
....
How is the maturity of game-ci CLI on macOS in general? Is this used already in production somewhere?
Thanks for the help!
Bug description
I built and installed game-ci CLI from source because of #272 .
It works to run
game-ci --help.But trying to build my project fails:
But, Unity Hub is installed in the default location. I did not change anything.
How to reproduce
Try to build a project on macOS with latest version.
The Unity project builds.
Additional details
AI says, the expected path contains a literal double-quote, which is why the actually correct path is not recognized.
Not sure if this is true, but the variable declaration does look suspicious to me.
See setup-mac.ts
How is the maturity of game-ci CLI on macOS in general? Is this used already in production somewhere?
Thanks for the help!