Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
1
Found in
5.6.3f1
Issue ID
1040333
Regression
No
Activating license from the command line fails if machine's binding key has changed
How to reproduce:
1. Open the current license file
2. Change Machine Binding Key="1" to other value
3. Execute in command line: Unity.exe -nographics -quit -batchmode -logFile "XXX/LicenceUpdate.log" -createProject "XXX/UnityTmpProject" -serial "I3-SOMEVALIDSERIAL" -username "YOURUSERNAME@unity3d.com" -password "YOURPASSWORD"
4. Check the generated log file after Unity quits
Actual result: Activation fails with a message "Cancelling DisplayDialog: Updating license failed Failed to update license within 60 seconds".
Expected result: Activation should succeed.
Reproducible with: 5.6.6f2, 2017.1.4p1, 2017.2.3f1, 2017.4.5f1, 2018.1.6f1, 2018.2.0b10, 2018.3.0a3.
Note:
Machine binding gets changed after Windows update (we are changing it manually to simulate it)
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
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
- Scene view has Y coordinates of the Screen Position node flipped when some of the URP features are disabled
- Volumetric fog shader variants are missing from build when "Strict Shader Variant Matching" is disabled
- Unnecessary modifications clutter the Scene when using a RectTransform driven by a LayoutGroup in a Prefab
- Files in the target folder are deleted without a proper warning when building an iOS project
Resolution Note (fix version 2020.2):
Fixed with 2020.2.0a8, backported to 2020.1.0b17, 2020.1.0b15, 2019.4.7f1