Search Issue Tracker

Won't Fix

Won't Fix in 3.12.X

Votes

0

Found in [Package]

3.12.1

Issue ID

HUBX-1302

Regression

No

License error message is vague when hardware has changed

Package: Hub

-

How to reproduce:
1. Navigate to “C:\ProgramData\Unity”
2. Open the “Unity_lic.ulf” file, with text editor of your choice
3. Change a few characters in the “MachineID Value” string
4. Save the file
5. Open Unity Hub
6. Open any project
7. Observe the Hub

Expected result: A pop up dialog box is displayed with descriptive message
Actual result: A pop up dialog box is displayed with vague message

Reproducible with: Unity Hub 3.12.1

Reproducible on: Windows 11
Not reproducible on: No other environments tested

Notes:
- Before reproducing the issue, with provided steps, it is advisable to save a copy of the file, so that later the license can be restored.
- Reproduction steps are simulating hardware changes.
- After performing hardware upgrades, the license is no longer valid. As a result we get a “License Error” dialog box with the message: “No valid Unity Editor license found. Please activate your license.”. The message is vague and doesn’t provide much assistance in figuring out what happened.

  1. Resolution Note:

    Thank you for reporting a bug to Unity.

    We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.

    Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

  2. Resolution Note (3.12.X):

    Thank you for reporting a bug to Unity.

    We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.

    Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

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.