Search Issue Tracker
Fixed in 1.0.0, 0.3.4, 0.2.7
Votes
1
Found in [Package]
0.2.6-preview
Issue ID
1253862
Regression
Yes
"Invalid effector for CustomOverlay attribute" error is thrown when getting assembly type's custom attributes
How to reproduce:
1. Open the user-supplied project "BugReportInvalidEffectorAttribute.zip"
2. Observe the Console
Expected result: no errors are thrown
Actual result: "Invalid effector for CustomOverlay attribute" error is thrown when BugReport.cs is executed
Reproducible with: 0.2.1-preview, 0.3.3-preview (2019.3.15f1, 2020.2.0a15)
Not reproducible with: 0.1.2-preview, 0.1.4-preview (2019.3.15f1)
Could not test with: 2018.4 (due to the package not being available)
Notes:
1. The full error:
Invalid effector for CustomOverlay attribute.
System.RuntimeType:GetCustomAttributes (bool)
BugReport:.cctor () (at Assets/BugReport.cs:13)
UnityEditor.EditorAssemblies:ProcessInitializeOnLoadAttributes (System.Type[]) (at /Users/builduser/buildslave/unity/build/Editor/Mono/EditorAssemblies.cs:114)
Comments (1)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
TP-Fab
Jul 21, 2020 09:17
Hi, any update on this? still happening every now and then.