Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2018.1.X
Votes
0
Found in
2017.1.1f1
Issue ID
949269
Regression
No
[WSA] Exported project does not have Visual Assets set correctly when open with Visual Studio 2017
Steps to reproduce:
1. Open the attached project
2. Switch platform to Windows Store
3. Build for WSA Universal 10 SDK
4. Open Visual Studio solution
5. Open manifest file -> Visual Assets
6. Observe, Unity sets only one row and completely missing 32px images
Expected result: Visual Assets should be set correctly
Actual result: Unity sets only one row and completely missing 32px images
Reproduced with: 5.5.4p5, 5.6.3p4, 2017.1.1p3, 2017.2.0f1, 2017.3.0b2
Fixed in: 2018.2.0a1
Backported to: 2018.1.0b9
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Add comment