Search Issue Tracker
Fixed
Fixed in 2022.3.62f1, 6000.0.46f1, 6000.1.0b15, 6000.2.0a9, 7000.0.0a27
Votes
1
Found in
2022.3.59f1
6000.0.40f1
6000.1.0b8
6000.2.0a5
Issue ID
UUM-99484
Regression
No
Warning that external text editor path does not exist when manually selecting specific code editors such as VSCodium or TextEditor
How to reproduce:
1. Open the project “IN-95687_BugReproducerURP”
2. Click (MacOS) Unity → Preferences → External Tools
3. Select the External Script Editor by clicking Browse… → VSCodium
4. In the Project window open the test.cs file
Expected result: Opens the test.cs file without any warnings
Actual result: Opens the test.cs file and gives a warning about the incorrect path
Reproducible with: 2022.3.59f1, 6000.0.40f1, 6000.1.0b8, 6000.2.0a5
Reproducible on: MacOS 12.7.4 (M1)
Not reproducible on: Windows 11
Notes:
- VSCodium or TextEditor is required to test this issue
- When the External Script Editor is selected, it says “… (internal)” next to the name.
- Using Visual Studio or Visual Studio Code does not produce this warning
- The “… (internal)” does appear on windows but the warning is not present
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- Crash on EnumerateDisabledKeywordsInVariantsArray or UNITY_XXH32 when rapidly saving ShaderGraph or VFXGraph changes
Add comment