Search Issue Tracker
Won't Fix
Votes
2
Found in
2017.4
2017.4.33f1
Issue ID
1193207
Regression
No
[macOS] MonoDevelop is not compatible with macOS Catalina
How to reproduce:
1. Create a new project
2. Go to Unity > Preferences > External Tools
3. Set External Script Editor to MonoDevelop
4. Create a new script
5. Double click the newly created script
Expected result: the new script opens in the MonoDevelop code editor
Actual result: the new script doesn't open
Reproducible with: 2017.4.34f1
Notes:
- MonoDevelop is not supported in any other versions than 2017.4
- MonoDevelop has to be installed and located in the External Script Editor tab. Using the "MonoDevelop (built-in)" option will open any other supported Script Editor.
- Only reproducible on Catalina macOS, other macOS versions open the script as expected
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
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note (2020.2.X):
We really appreciate your contribution to the Unity product. Thank you for reporting this issue. We take every case submitted to us seriously by investigating the impact on you, our customer, as well as the impact it may have on the engineering and experience of our product.
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this issue.
If you need MonoDevelop to be supported for your project, an opportunity would be to implement an instance of this type: https://docs.unity3d.com/ScriptReference/Unity.CodeEditor.IExternalCodeEditor.html
This instance would need to be registered during InitializeOnLoad using this api: https://docs.unity3d.com/ScriptReference/Unity.CodeEditor.CodeEditor.Register.html
This way you can have custom support for any code editor. The built-in support that we fall back to for non-supported code editors, will not handle special cases some code editors require. This API is the same used for our ide packages.