UNITY problem Unmet requirements: Exists=>unity\.path\.2019\.4\.10.* exists
I am having trouble getting a custom version of Unity to work. We are developing for PS5 and that requires a custom download of Unity, that version refuses to install on the HUB directory (due to custom path in the installer, not from us) So the best I can do is install it on
C:\Program Files\Unity\Hub\Editor\2019.4.10f1\Editor
And then move it to
C:\Program Files\Unity\Hub\Editor\2019.4.10f1
Which I believe is where the standard 2019.4.10f1 version of Unity would install, and this I verified would work fine with TeamCity since I had things working prior to this custom Unity install.
Now I just get a
Unmet requirements: Exists=>unity\.path\.2019\.4\.10.* exists
I have tried: ( since initially the install wanted to install in C:\Program Files\Unity\Editor")
Setting UNITY_HINT_PATH to C:\Program Files
Looking at %agent%-> Agent Parameters -> Configuration Properties. There is no unity.path listed there are all. (I have restarted the agent many many times)
Installing the darn thing in just about every directory that I thought would work...
Now I am out of ideas. Can anyone help?
How can I tell the agent where to look for Unity ?
Please sign in to leave a comment.
Hello,
Could you please let me know if this is the plugin in use (https://github.com/JetBrains/teamcity-unity-plugin)? If my guess is correct, here is how the plugin performs Unity detection:
1) hint paths are evaluated (as per https://github.com/JetBrains/teamcity-unity-plugin/blob/master/plugin-unity-agent/src/main/kotlin/jetbrains/buildServer/unity/UnityDetectorBase.kt#L44 method, UNITY_HOME, UNITY_HINT_PATH and PATH are being parsed);
2) for each path in use, agent will check if there is either a folder which name starts with Unity, or a path containing Unity/Hub/Editor (see https://github.com/JetBrains/teamcity-unity-plugin/blob/master/plugin-unity-agent/src/main/kotlin/jetbrains/buildServer/unity/UnityDetectorBase.kt#L87);
3) suitable paths will be checked further according to the environment; on Windows, it will check for the Editor/Unity.exe inside of the path.
All checks are covered by logging, so you could enable debug logging on agent side as described here: https://www.jetbrains.com/help/teamcity/viewing-build-agent-logs.html#Generic+Debug+Logging, and then restart agent so it performs another check on the start, then access teamcity-agent.log to see what directories were checked (so to see if it even considers the actual installation folder) and what were the results. If you could share the log with me by the means of https://uploads.jetbrains.com, I would gladly assist with analysis.
Hi Fedor,
I have encountered the same issue as Nospam.
I check the TeamCity agent log, the TeamCity Unity Plugin did check the Unity 2019 directory, but it failed to find the Unity (line 1630 in the log).
I have upload the log, the upload id is 2020_11_02_y7pvrwE39r4BFuD2 (file: teamcity-agent.log).
Could you please help to check this issue? It breaks our continuous integration process.
Thank you very much.
Hello Yongyi!
Thank you for the log file; I am checking what could lead to this behavior now. Could you please confirm the contents of C:\Users\BIG-DATABASE\AppData\Roaming\UnityHub\hubInfo.json file?(e.g. does it specify the 2019.4 folder as Unity installation?)
Hi Fedor,
There is only one line in C:\Users\BIG-DATABASE\AppData\Roaming\UnityHub\hubInfo.json, which is:
{"version":"2.4.3","executablePath":"C:\\Program Files\\Unity Hub\\Unity Hub.exe"}
Hello Yongyi,
From the plugin code it appears that for every "Looking for Unity installation in" line in log, plugin would attempt to locate "Editor/Unity.exe" inside of the folder. With this in mind, I suspect that the below path exists:
and this one does not:
Could you please confirm actual paths for the Unity.exe on this agent?
Hi Fedor,
The path of Unity 2019 does exist.
I have uploaded the screenshot of the folder, the upload id is: 2020_11_03_AFxNfc3E4gMgrySW (files: UnityHub.jpg, Unity2019Path.jpg)
Hello Yongyi,
Thank you! I have just reached out to the development team; the current plan is to improve the log coverage (as currently it`s either the installation is correctly detected or not, with no verbosity as to why installation was not detected) and to provide you with a debug version of plugin - please see this issue on our tracker I have just created: https://youtrack.jetbrains.com/issue/TW-68480
As soon as it is available, I will get back to you. If you wish, you could also subscribe to the issue updates so to be notified as soon as it is ready.
Hello Yongyi,
First of all, a plugin version with extra debug logging is available: https://teamcity.jetbrains.com/repository/download/TeamCityUnityPlugin_Build/3184001:id/teamcity-unity-plugin.zip
Speaking of the issue itself, could you please try to run "Locate" option within UnityHub and point it to the 2019.4.13 installation? As per the development team tests with newly installed editor, after agent restart Unity version has been successfully detected.
Hello Fedor,
I have run the "Locate" option and restart the build agent, but 2019 is still not been detected.
But I am not able to download the plugin from https://teamcity.jetbrains.com/repository/download/TeamCityUnityPlugin_Build/3184001:id/teamcity-unity-plugin.zip
Hello Yongyi,
Could you please use a "Submit a request" option at the top of the page and reference this thread (so the request is assigned to me and I could send over the plugin to you directly)?
Hi Fedor,
I have submitted a request.
Hi Fedor,
I have come across the root cause.
It seems the Unity plugin cannot find Unity 2019.4.13 f1c1 which is a special version of Unity for China mainland.
I have installed Unity 2019.4.13 f1, the Unity plugin find it as expected.
Thanks a lot for you help.
Hello Yongyi,
Thank you for the notice! I will check with the development team if the pattern for version postfix has to be updated in scope of https://youtrack.jetbrains.com/issue/TW-68480.