Search Issue Tracker
By Design
Votes
0
Found in
Issue ID
804488
Regression
No
Activation from command line fails on 4.7.2 on staging
Repro:
1. Try to activate editor from command line with e.g. ./Unity -licenseserver license-staging.hq.unity3d.com -activationserver activation-staging.hq.unity3d.com -quit -batchmode -serial R3-PSRX-XXXX-JN7V-KCCY-XXXX -username 'raminta+XXXxx@unity3d.com' -password 'XXXxxx123'
2. Observe that Editor icon bounces for few seconds when closes, but license file is not created, Editor is not activated
Editor: 4.7.4
Environment: Staging
OS: OS X 10.11.4
Note: activation from command line works on 5.x.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Add comment