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
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
- White lighting artifact when a point light with a small emission range and "Hard Shadows" touches an object while a directional light with "Soft Shadows" and another point light are present
TP-Fab
Jul 21, 2020 09:17
Hi, any update on this? still happening every now and then.