Search Issue Tracker
Fixed in 2019.2.X
Votes
0
Found in
2018.2.0a2
2018.3.0b5
Issue ID
1089749
Regression
Yes
Building app leads to meanless errors when UnityEngine.XR.WSA namespace is used
How to reproduce:
1. Open attached Unity project "1089749_bug"
2. Build project
Expected result: Error with information about not existing namespace pops up.
Actual result: Build fails without any information what causes this problem.
Regression first introduced on: 2018.2.0a2
Reproduced with: 2019.1.0a6, 2018.3.0b6, 2018.2.13f1
Not reproduced on: 2017.4.13f1
Devices under test:
Reproduced on:
VLNQA00137, Samsung Galaxy S9+ (SM-G965F), Android 8.0.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00155, Meizu PRO 7 Plus (PRO 7 Plus), Android 7.0, CPU: MediaTek Helio X30 MT6799, GPU: PowerVR Rogue Marlowe
iOS
Windows Standalone
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment