Search Issue Tracker
Active
Votes
0
Found in
9.2.1
Issue ID
UUM-132360
Regression
No
Android build fails with “The Composition Layers Support feature is required to use the Composition Layers package…” error
Reproduction steps:
1. Create a new VR template project
2. File > Build Profiles > Build
3. Observe the Console
Actual result: “The Composition Layers Support feature is required to use the Composition Layers package…” error is thrown
Expected result: No warnings or errors are thrown
Reproducible with: 2.3.0 (6000.4.0b5)
Reproduced on: Windows 10, macOS Sequoia 15.3 (Intel)
Note:
- Fixing issue in Project Validation window makes issue not reproducible
- No other versions tested as testing takes significant amount of time
- Full errors:
{code:java}
The Composition Layers Support feature is required to use the Composition Layers package.
UnityEditor.EditorApplication:Internal_CallDelayFunctions ()
{code}
{code:java}
Double click to fix OpenXR Project Validation Issues.
UnityEditor.EditorApplication:Internal_CallDelayFunctions () {code}
{code:java}
BuildFailedException: OpenXR Build Failed.
UnityEditor.XR.OpenXR.OpenXRProjectValidationBuildStep.OnPreprocessBuild (UnityEditor.Build.Reporting.BuildReport report) (at ./Library/PackageCache/com.unity.xr.openxr@ef0033a586bf/Editor/OpenXRProjectValidationRulesSetup.cs:235)
UnityEditor.Build.BuildPipelineInterfaces+<>c__DisplayClass17_0.<OnBuildPreProcess>b__1 (UnityEditor.Build.IPreprocessBuildWithReport bpp) (at <442a466f60504df9a8dd7d731828931c>:0)
UnityEditor.Build.BuildPipelineInterfaces.InvokeCallbackInterfacesPair[T1,T2] (System.Collections.Generic.List`1[T] oneInterfaces, System.Action`1[T] invocationOne, System.Collections.Generic.List`1[T] twoInterfaces, System.Action`1[T] invocationTwo, System.Boolean exitOnFailure) (at <442a466f60504df9a8dd7d731828931c>:0)
UnityEditor.EditorApplication:Internal_CallDelayFunctions() {code}
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
Add comment