[UnityConnectServicesConfig] config is NOT valid, switching to default about docker HOT 5 CLOSED

This is most likely not a bug. Mostly every time when unity outputs "config is NOT valid", it means the config is indeed not valid.

A few things to check:

• all variables are set in your secrets and properly passed to the action (typos happen)
• special characters in your password (known issue with unity)
• in case of private license, provide the .ulf file, not the .alf file
• in case of pro or other license, make sure you can log in to the unity website and make sure that your license has open seats or actrivations

Please let us know if that does not solve your problem.

from docker.

@webbertakken I've verified as many of the variables as possible and they all check out. There's no special characters in our password. We use a pro license we our extension on the license is .alf. I can login to Unity portal no problem.

from docker.

Note that .alf is the activation license file, not the actual license file.

Note that pro license uses a serial to activate, not the file as per the documentation.

from docker.

I was able to activate the license already and got the serial number and everything. I've added it to my GitLab pipeline as well.

In case you're wondering why there's 2 UNITY_LICENSE variables I created the UNITY_LICENSE_CONTENT for testing.

from docker.

It looks like you followed both the personal activation flow as well as the professional activation flow. This will not work; you should follow only the professional activation flow.

Internally when you have UNITY_LICENSE set, it will skip the activation flow of pro licenses, which are serial based.

Both workflows are used by many users. There are no known bugs.

from docker.