Search Issue Tracker
Active
Votes
0
Found in
6000.0.62f1
6000.2.13f1
6000.3.0f1
6000.4.0a5
6000.5.0a1
Issue ID
UUM-128203
Regression
No
The Unity Version Control window refers to Explorer instead of Finder when running on macOS
How to reproduce:
1. Create a new project with “Use Unity Version Control“ checkbox enabled (it can be found under the “Location” setting in Unity Hub)
2. In the “Unity Version Control” window, click on the “Create workspace” button
3. After the window updates, click on the “Create workspace” button again
4. In the “Pending Changes” tab, right-click on any file and navigate to the “Open” submenu
5. Observe the “Open in explorer“ option
Expected result: The option name is "Open in Finder"
Actual result: The option name is "Open in explorer"
Reproducible with: 2022.1.0a5, 6000.0.62f1, 6000.2.13f1, 6000.3.0f1, 6000.4.0a5, 6000.5.0a1
Reproducible on: macOS 15.3.2 (24D81) (M1 Max)
Not reproducible on: No other environments tested
Note: Right-clicking any .meta file shows the “Open .meta in explorer” option, which could also be considered for a fix
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Some Build Profile settings do not remain checked when launching a project without the /Library folder through the command line
- TextMeshPro gradient tags render as literal text when using a font that contains only a part of the ASCII character set
- Small rectangles appearing in the corner of title text in Editor when System Font and Bitmap are selected in preferences
- The shortcut character is typed into the name field when a [Shift + <any alphanumeric key>] shortcut is used to create the asset from "Asset/Create"
- TextMeshPro ligatures broken when Font Style setting is changed from “Lowercase” to “Uppercase”
Add comment