Search Issue Tracker
By Design
By Design in 6000.5.X
Votes
0
Found in
6000.5.0a5
Issue ID
UUM-133201
Regression
No
Project Auditor throws "Invalid Code Analysis Areas" pop-up when "None" Project Area is selected
Steps to reproduce:
1. Create new Unity project
2. Open Project Auditor window (Window > Analysis > Project Auditor)
3. In Project Areas select "None" only
4. Install Rules
5. Once installed, press Start Analysis
6. Observe the pop-up
Actual results: "Project Areas" allows selecting "None", throwing pop-up "No Project Areas select" and "Invalid Code Analysis Areas", not allowing to perform any analysis
Expected results: "Project Areas" should not have "None" section
Reproducible with versions: 6000.5.0a3, 6000.5.0a5
Can’t test with versions: 6000.4.0b6 (different Project Auditor window UI, no "Project Areas"), 6000.5.0a1 - 6000.5.0a2 (switches automatically to "All" instead of "None")
Tested on (OS): Ubuntu 24.04
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
Resolution Note:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.