Search Issue Tracker

Fixed

Won't Fix in 1.1.X

Fixed in 1.3.4

Votes

75

Found in [Package]

1.1.29

1.3.3

Issue ID

DSTR-370

Regression

No

"Unable to find player assembly" warnings logged to the Console when building an empty URP project with Burst and Jobs

Package: Test-Framework

-

How to reproduce:
1. Create a new empty URP project
2. Import the Burst package
3. Import the Jobs package
4. Build the project
5. Observe the Console in the Editor

Expected result: no warnings are logged in the Console
Actual result: several warnings are logged in the Console

The warnings are:
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.
UnityEditor.Scripting.ScriptCompilation.EditorCompilationInterface:CompileScripts (UnityEditor.Scripting.ScriptCompilation.EditorScriptCompilationOptions,UnityEditor.BuildTargetGroup,UnityEditor.BuildTarget,int,string[])
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.
UnityEditor.Scripting.ScriptCompilation.EditorCompilationInterface:CompileScripts (UnityEditor.Scripting.ScriptCompilation.EditorScriptCompilationOptions,UnityEditor.BuildTargetGroup,UnityEditor.BuildTarget,int,string[])

 

Reproducible with: 1.1.27, 1.1.29 (2019.4.30f1, 2020.3.17f1, 2021.1.18f1, 2021.2.0b9, 2022.1.0a7)

Notes:
Also reproducible with HDRP

  1. Resolution Note (1.1.X):

    This issue will only be fixed in 1.3.x as the fix is too invasive to be released in 1.1.x.

Add comment

Log in to post comment