Search Issue Tracker
Fixed in 2017.4.0
Fixed in 2017.4.X
Votes
5
Found in
2017.4.0f1
2017.4.33f1
2018.1.0a1
Issue ID
1191344
Regression
No
[macOS][2017.4] Empty error appears in the Console window when certain files are present in the project with macOS Catalina
How to reproduce:
1. Download the tester-attached script(uv_anim.js)
2. Create a new Unity project
3. Import the downloaded script
4. See the Console window
Expected result: no errors are thrown
Actual result: an empty error appears in the Console window; it cannot be cleared
Reproducible with: 2017.4.33f1, 2018.1.0a7
Not reproducible with: 2018.1.0b1, 2018.1.9f2, 2018.4.11f1, 2019.2.10f1, 2019.3.0b7, 2020.1.0a9
Notes:
Tested with macOS Mojave 10.14.6 and macOS Catalina 10.15; only reproduced with the latter
-
WermHat
Dec 28, 2019 16:20
Here is the forum thread where we are still actively pushing for a fix: https://forum.unity.com/threads/macos-catalina-blank-error-appears-with-no-info.761903/
-
excalith
Nov 22, 2019 12:55
So long LTS, and thanks for all the fish!
-
WermHat
Nov 20, 2019 02:13
2017.4 is the last LTS that supports UnityScript. This absolutely needs to get fixed. The entire point of the LTS system is to prevent critical, workflow-destroying bugs like this.
-
strobegen
Nov 13, 2019 15:56
With this bug 2017.4 LTS not usuable at all on MacOs so literally it's already the end of life for this version.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2017.4):
Fixed in 2017.4.40f1