Search Issue Tracker
Fixed in 5.3.6
Votes
0
Found in
5.3.3p2
Issue ID
775624
Regression
Yes
[UWP] StoreLogo.png name is used instead of StoreLogo.scale-100.png
StoreLogo.png name is used instead of StoreLogo.scale-100.png. This gives an error in Visual Studio and the asset isn't included
Fun fact: solution built on IL2CPP backend allows to use "StoreLogo.scale-100.png", while solution built on .NET backend throws error.
Reproduced on 5.3.5f1.
Not an issue on latest 5.4.0b18.
Steps for 5.3.5f1
1. Create new project.
2. Build to WSA 8.1 or WSA Universal 10 platform.
3. Run WACK.
4. Visual Studio throws error:
App manifest references the image 'Assets\StoreLogo.png' which does not have a candidate in main app package.
Workaround: Rename "StoreLogo.png" to "StoreLogo.scale-100.png"
---
Steps for version 5.3.3p2
Repro steps:
1. Open any project
2. Set Store Logo 100% (50x50)
3. Build
4. Open the generated solution -> Manifest File -> Visual Assets
5. See, that there is an error (https://gyazo.com/b99240480297d25ecbdd4a7a48bddbb9)
Workaround: Rename "StoreLogo.png" to "StoreLogo.scale-100.png"
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- IndexOutOfRangeException occurs when entering "<a></a>" tags in a TextMeshPro UI field
- Numeric property drag cursor gets enabled in the Inspector Preview window when the window is above numeric properties
- UI elements become unusable due to Object and Text Fields being set to empty/"0" when clicking "Reset" on their Components
- Scene Asset is not attached to a Lighting Data Asset for a URP Package Sample Scene
- Gizmos are not rendered for the Base Camera when using Camera Stacking
Add comment