Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4.0f1
2019.1.14f1
2019.2.0a1
Issue ID
1187264
Regression
No
[UWP][19.2] Build fails when using Burst with Mixed Reality Toolkit
Steps to reproduce:
1. Download attached project
2. Switch platform to UWP
3. Build project
Results: Build will fail with a Burst compiler failed running and Failed to resolve assembly exceptions.
Reproduced with: 2019.2.8f1
Not reproducible with: 2020.1.0a7, 2019.3.0b5, 2018.4.10f1
Mono.Cecil.AssemblyResolutionException: Failed to resolve assembly: 'Windows.Foundation.FoundationContract, Version=3.0.0.0, Culture=neutral, PublicKeyToken=null'
at Mono.Cecil.BaseAssemblyResolver.Resolve(AssemblyNameReference name, ReaderParameters parameters)
at Burst.Compiler.IL.AssemblyLoader.Resolve(AssemblyNameReference name)
at Mono.Cecil.MetadataResolver.Resolve(TypeReference type)
at Mono.Cecil.TypeReference.Resolve()
at Burst.Bcl.BclApp.FindExecuteMethods(List`1 rootAssemblyPaths)
at Burst.Bcl.BclApp.GetMethodsToCompileBeforeDynamicDispatch()
at Burst.Bcl.BclApp.GetMethodsToCompile()
at Burst.Bcl.Program.Main(String[] args)
BuildFailedException: Burst compiler (1.2.0-preview.5) failed running
stdout:
An unexpected exception occurred:
stderr:
Mono.Cecil.AssemblyResolutionException: Failed to resolve assembly: 'Windows.Foundation.FoundationContract, Version=3.0.0.0, Culture=neutral, PublicKeyToken=null'
at Mono.Cecil.BaseAssemblyResolver.Resolve(AssemblyNameReference name, ReaderParameters parameters)
at Burst.Compiler.IL.AssemblyLoader.Resolve(AssemblyNameReference name)
at Mono.Cecil.MetadataResolver.Resolve(TypeReference type)
at Mono.Cecil.TypeReference.Resolve()
at Burst.Bcl.BclApp.FindExecuteMethods(List`1 rootAssemblyPaths)
at Burst.Bcl.BclApp.GetMethodsToCompileBeforeDynamicDispatch()
at Burst.Bcl.BclApp.GetMethodsToCompile()
at Burst.Bcl.Program.Main(String[] args)
Comments (1)
-
Jieyang666
May 03, 2022 08:23
same problem
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:
Fixed in 2018.4.10f1 and 2019.3.0b5