Search Issue Tracker
Active
Under Consideration for 3.14.X
Votes
0
Found in [Package]
3.14.2
Issue ID
HUBX-1493
Regression
No
Setting up Unity Version Control for a project in the Hub does not actually set it up in the Editor when the project has a long name
Steps to reproduce:
- Open Unity Hub
- Create a new project without version control and a very long project name (max characters allowed)
- Once the project is created and opened, exit the Editor
- Hover the mouse over the Unity Version Control icon for the project in the Hub
- Click "Use Unity Version Control"
- Press the "Connect to Version Control"
- Once the Editor is opened, Open the Unity Version Control window (Window > Version Control > Unity Version Control)
- Observe the Unity Version Control window
- Close the Editor
- Observe the Hub
Actual results: Unity Version Control is not set up in the Editor, but shows as set up in the Hub
Expected results: Unity Version Control is set up in the Editor and the Hub
Reproducible with versions: 3.14.2
Tested on (OS): macOS Silicon Sequoia 15.6.1
Notes:
- After reproduction, it seems that clicking the "Disconnect from version control" button in the Hub does nothing, it still keeps showing that the version control is connected for the project
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Shader Graph Swizzle Node Input/Output and Mask Update Incorrectly After Undo
- [URP] Crash on GameObject::QueryComponentByType when baking a Reflection Probe in an unsaved/untitled Scene
- No Icons are used for the Entry and Exit States in the Inspector when selected in an Animator Controller
- Crash on PlayerMain(int, char const**) when exiting Standalone Player with a Particle System in the Scene
- No Icon is used for the Runtime Animator Controller Type in a Search Window when assigning an Animator Controller in the Animator Component
Add comment