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
- Incorrect Burst Exception Control Flow in Editor due to Mono Handling of calli instruction
- [Linux] Packman options to add package from Git URL doesn't always show the window directly below the + button
- Editor redirects to a broken page when pressing question mark "?" in the Inspector window
- Editor directs to non-existent page when pressing "Learn more..." for Asset Pipeline
- "Cyclic Prefab nesting not supported" error window is thrown when trying to nest two sibling prefab variants
Resolution Note (fix version 2020.2):
Fixed with 2020.2.0a8, backported to 2020.1.0b17, 2020.1.0b15, 2019.4.7f1