Search Issue Tracker
By Design
Votes
1
Found in
2018.4
2019.4.4f1
2021.1
Issue ID
1278407
Regression
No
UWP Player Settings missing Capability backgroundSpatialPerception Setting
How to reproduce:
1. Create a new project
2. Switch to UWP
3. Open the Project Settings -> Player -> Publishing Settings -> Capabilities section
4. Search for "backgroundSpatialPerception" Setting
Expected result: There is a checkbox for "backgroundSpatialPerception" Setting
Actual result: There is no checkbox for "backgroundSpatialPerception" Setting
Reproducible with: 2018.4.29f1, 2019.4.14f1, 2020.1.12f1, 2020.2.0b10, 2021.1.0a3
Update: This is a feature request.
Unity only exposes a subset of the total UWP Capabilities in the Editor that are common to many Unity applications while excluding less common Capabilities, especially "restricted" ones. This feature is a convenience only; any Capability can be added directly into the package.appxmanifest within the generated Visual Studio solution.
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
- [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
- [RenderingDebugger][InputSystemPackage] Ctrl+Backspace shortcut doesn't work to open the Rendering Debugger when New Input System is in use
Resolution Note (2022.2.X):
We have avoided adding the backgroundSpatialPerception capability as this is restricted by Microsoft (requires permission to publish to Windows Store with the Capability set) due to privacy concerns, and could be easily confused with the non-restricted spatialPerception capability.
As described in https://docs.unity3d.com/Manual/class-PlayerSettingsWSA.html you can set this capability in the generated Visual Studio solution. Unity stores these settings in the Package.appxmanifest file when creating a Visual Studio solution for the first time. Unity doesn’t overwrite the Package.appxmanifest file if it’s already present. That means if you change any of the Player settings, you need to check Package.appxmanifest. If you want to regenerate Package.appxmanifest, delete it and rebuild your project from Unity.
We might revisit this feature request in the future but for now the suggested workaround is to add it from the Visual Studio solution as described above.