Search Issue Tracker
Won't Fix
Won't Fix in 1.1.X
Votes
0
Found in [Package]
1.1.0
Issue ID
ECSB-53
Regression
Yes
'Script will not be compiled' warnings appear in the Console when adding the 'Collections' package
Reproduction steps:
1. Create a new Unity project
2. Go to the 'Window -> Package Manager'
3. Click the add button in the status bar and select 'Add package by name'
4. Add the 'com.unity.collections’ package with version ‘1.1.0’
Expected result: No warnings are in the Console
Actual result: 'Script will not be compiled' warnings are in the Console
Reproducible with: 1.1.0 (2021.3.5f1, 2022.1.8f1)
Not reproducible with: 1.1.0 (2020.3.36f1, 2022.2.0a18, 2023.1.0a2), 1.2.3-pre.1 (2021.3.5f1), 1.3.1 (2021.3.5f1)
Reproducible on: macOS 12.4 (Intel)
Warnings:
- 'Script 'Packages/com.unity.collections/DocCodeSamples.Tests/CollectionsAllocationExamples.cs' will not be compiled because it exists outside the Assets folder and does not to belong to any assembly definition file.'
- 'Script 'Packages/com.unity.collections/DocCodeSamples.Tests/CollectionsExamples.cs' will not be compiled because it exists outside the Assets folder and does not to belong to any assembly definition file.'
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
- Points Lights are getting culled prematurely when using Forward+ and Deferred+ rendering paths
- Search's Indexing settings in the Preferences window are not searchable
- Crash on block_locate_free when opening a specific project
- "Project connected" pop opens again after closing it
- Cloud Code Authoring logs "JsAssetHandler:OpenAsset (int,int) does not match any of [OnOpenAssetAttribute] expected signatures" when opening or switching scenes and having the Deployment Package Installed
Resolution Note:
Affected versions seem wrong, because this issue is fixed in Collections 1.2.3, and bug only mentions 1.1.0.
Resolution Note (1.1.X):
Affected versions seem wrong, because this issue is fixed in Collections 1.2.3, and bug only mentions 1.1.0.