Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
1
Found in
2019.2.17f1
2019.3
2020.1
Issue ID
1220634
Regression
No
[Licensing] Editor cannot talk to client if username has unicode characters
Reproduction steps:
1- Create an account with a username containing a character such as 'ß'
2- Start Unity from that account
Expected Result:
Editor should be able to talk to Unity.Licensing.Client if username has special characters.
Actual Result:
Editor cannot talk to Unity Licensing Client if user name has Unicode characters.
Although this was reported in closed network but it should be applicable in open network.
Success Criteria:
Editor can talk to licensing client if user name has special characters.
Implementation Notes:
Normalize the username and pass to Client.
Default Licensing Client user name extraction should be same as the one that editor uses.
Environment: Windows
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment