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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment