Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.2.7f1
Issue ID
UUM-28762
Regression
No
ULF License check fails if the file name contains a "."
Reproduction steps:
1. Navigate to %ProgramData%/Unity (Library/Application Support/Unity on macOS)
2. Rename Unity_lic.ulf to Unity.lic.ulf
3. Restart the Hub
Expected result: License check works
Actual result: License check fails
Reproducible with: 3.4.1-Beta, 3.4.1
Licensing client version 1.12.0 3acf7bc
Reproducible on: macOS 12.4 (Intel), Windows 10 (user's)
Note from reporter: When activating a license with an ALF, the downloaded ULF license is named in such a way that it does not work by default. For example: Unity_v2022.x.ulf
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Resolution Note:
There is no expectation that the license will still work if it is renamed, even though the file remains in-place and the .ulf extension is preserved.
Licensing code will not consume *.ulf in that directory; it must be named Unity_lic.ulf exactly.
Also, no matter what the name of the file is once it is downloaded, the manual stipulates that, in order to activate that file, the command should be:
<editor-command-location> -batchmode -manualLicenseFile <yourUlfFile> -logfile
This command will copy the file into the license directory, and rename it.
The same thing happens if, using the Hub for manual license activation flow: in Preferences->Licenses->Add button->Activate with license request (at the 3rd step: "Activate with license").
Accordingly, if we have Unity_v2022.x.ulf, and it is moved into C:\ProgramData\Unity (or to /Library/Application\ Support/Unity on MacOS, as the case may be), it makes no difference if it is renamed to just Unity_v2022.ulf, as it will not be recognized.