Search Issue Tracker

Fixed in 2018.3.X

Fixed in 2018.1.X, 2018.2.X

Votes

0

Found in

2018.1.0b6

2018.1.0b10

Issue ID

1041582

Regression

Yes

License activation fails when running Unity with command line arguments

Deployment Management

-

How to reproduce:
1. Delete C:\Users\[USERNAME]\AppData\LocalLow\Unity\Browser folder
2. Delete C:\ProgramData\Unity\unity_lic.ulf file
3. In Command Prompt: cd C:\Program Files\2018.1\2018.1.0b6_2c4679632cfb\Editor
4. In Command Prompt: start /b /wait Unity.exe -quit -batchmode -serial "I3-XXXX-XXXX-XXXX-XXXX-XXXX" -username "YOUR@EMAIL.COM" -password "YOURPASSWORD" -logFile C:\Users\[USERNAME]\Desktop\log

Expected result: Unity activates license
Actual result: Unity fails to activate license

Reproduces with: 2018.1.2f1, 2018.2.0b6
Not reproducible with: 2018.1.0b5

Note: The /b /wait is just so to wait for Unity to run and then exit. Unity license directory: C:\ProgramData\Unity\unity_lic.ulf.

Log file: "Updating license failed Failed to update license within 60 seconds. Exiting. This should not be called in batch mode.
(Filename: C:\buildslave\unity\build\Editor/Platform/Windows/EditorUtility.cpp Line: 1151)"

Fixed in: 2018.3.0a1, 2018.2.0b9, 2018.1.5f1
Log in to vote on this issue

Comments (3)

  1. nick_nearlight

    Oct 23, 2019 16:25

    This appears to be re-occuring in 2019.2.5f1

  2. jasonatkaruna

    Mar 01, 2019 17:56

    I reproduced this in 2018.3.6f1

  3. StephenHodgson-Valorem

    Jan 11, 2019 21:03

    I am able to reproduce this in 2018.3.0f1

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues