Search Issue Tracker
Fixed
Fixed in 2022.3.17f1, 2023.2.5f1, 6000.0.0b1
Votes
3
Found in
2022.3.13f1
2023.1.20f1
2023.2.0b18
2023.3.0a14
6000.0.0b11
Issue ID
UUM-55690
Regression
Yes
Scripts are not compiled when using certain folder/asmdef configurations in the Assets folder
How to reproduce:
1. Open the attached Project "TEST_SCRIPTCOMPILE_2.zip"
2. Observe the Console
Expected result: Compilation errors are present in the Console
Actual result: No errors are present in the Console
Reproducible with: 2022.2.0a13, 2022.3.13f1, 2023.1.20f1, 2023.2.0b18, 2023.3.0a14
Not reproducible with: 2021.3.32f1, 2022.2.0a12
Reproduced on:
- MacOS (13.5.2, Intel) Editor
- Windows 10 Editor (User-supplied information)
Notes:
- In the provided Project changing the names of the folders "in" and "in2" to something without "in" makes the issue not reproducible
- Removing any of the asmdef files in the Project makes the issue not reproducible
- Moving the Script in the project to the Assets folder, or to any of the folders containing the asmdef makes the issue not reproducible
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note (fix version 6000.0.0b1):
Closing the ticket the PR with a fix has landed in 2023.3.0b1