Search Issue Tracker
Fixed in Unity 2017.1
Votes
0
Found in
5.5.1f1
Issue ID
892653
Regression
No
[WSA] FieldAccessException is thrown when running the WSA build
Steps to reproduce:
1. Open the attached project
2. Open the Assets/testScene.unity scene
3. Switch platform to Windows Store
4. Build for WSA Universal 10 SDK, Build type - XAML
5. Open Visual Studio solution
6. Deploy on local machine (Debug or Release)
7. Observe the errors in the Output console
Expected result: Errors should not appear in the Output console
Actual result: Errors appear in the Output console
Note:
Not reproducible with Master mode
TrashMetalData trashMetalData = Resources.Load<TrashMetalData>("TrashMetalData"); :10 TestResourceLoader.cs thrown exception
Reproduced with: 5.4.5p1, 5.5.2p4, 5.6.0f2, 2017.1.0a5
Fixed in: 2017.1.0b4
Backported to: 5.6.1p1, 5.5.4p1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Unity crash in SerializedFile::ReadMetadata<false> when AssetBundle. LoadFromMemory() is called
- ProceduralMaterial.ClearCache() on "Do Nothing" Substance triggers RebuildTextures
- Setting "Default Behavior Mode" to "2D" breaks HDR rendering
- Crash in GdipCreateBitmapFromStream when calling System.Drawing.Bitmap constructor
- DLL files are not excluded during building for standalone platform, even though they are selected to be excluded
Add comment