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)
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
- Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note:
Fixed in 2018.4.10f1 and 2019.3.0b5