Search Issue Tracker
Fixed in 5.3.5
Votes
0
Found in
5.3.3f1
Issue ID
780971
Regression
No
[UWP] Package.appxmanifest generated incorrectly when specifiying a protocol
If you specify a protocol in the build settings for a WSA application, your project cannot be built anymore as the Package.appxmanifest is improperly generated
---
Generated:
<Extensions>
<Extension Category="windows.protocol">
<Protocol Name="unity-azme" />
</Extension>
</Extensions>
---
Expected:
<Extensions>
<uap:Extension Category="windows.protocol">
<uap:Protocol Name="unity-azme" />
</uap:Extension>
</Extensions>
Fixed on 5.4.
Reproducible on 5.3.
Repro steps:
1. Create an Empty Project.
2. Add a protocol name in the WSA settings.
3. Build the project for WSA Universal 10.
4. Open the project in Visual Studio.
5. Try to open the Package.AppxManifest. Error appears "Unable to Load Manifest Designer".
Workaround: Edit protocol tags in Package.AppxManifest.
Comments (1)
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
flashmandv
Jan 28, 2017 15:35
Happens to me with the latest beta Unity 5.6.0 (also with official release 5.5.1)
I can run my project in VS, but I can't export for Windows 10 Store. It shows 45000 errors. But I rebuild successfully and it runs OK. ?!? how