Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2018.3.X
Votes
10
Found in
2018.1.0b12
2018.1.0f2
2018.2.0a3
Issue ID
1038153
Regression
Yes
Selecting custom MenuItem from Component tab results in "can't be checked because doesn't exist" error message
How to reproduce:
1. Open the attached "1038153_repro.zip" project
2. In the main menu, select Component/Component lister
Expected result: "ComponentList" window is opened without error messages.
Actual result: "ComponentList" window is opened, but with a console error message "Menu Component/Component lister can't be checked because doesn't exist".
Reproducible with - 2018.1.2f1, 2018.2.0b5
Not reproducible with - 2017.4.3f1, 2018.1.0b11, 2018.2.0a2
Notes:
- The issue does not seem to reproduce when custom MenuItem is created on the main menu tabs, other than "Component".
- The issue is reproducible only when selecting the Component/Component lister for the first time. Subsequent attempts result in the expected behavior.
- If the issue does not reproduce from the first attempt, press "Clear" in the Console window and repeat step 2.
- The issue occurs again after script recompile.
Fixed in 2018.3.0a11
Backported to 2018.2.13f1
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
- Long Prefab save times when using Unity 2022.2 and higher
- Console displays error "UnityException: Creating asset at path Assets/Scenes/ .scenetemplate failed." during scene template saving
- "Development Build" watermark is shown in non-development UWP release builds
- Console errors appear when the Inspector is set to Debug and a GameObject is selected
- A script public variable value is not used when set in the Inspector window
AdamGoodrich
Jul 13, 2018 07:23
We are getting a lot of complaints about this with CTS. Works on previous 5.x and 2017.x and not on 2018.x, and people just assume that our product is at fault.
Can't seem to find a fix or work around for this anywhere!
amisner2k
Jul 07, 2018 04:33
This also happens to me on 2018.1.2f1. It's easily reproducible as it tends to popup frequently when doing pretty much anything in the editor.