Search Issue Tracker
Won't Fix
Won't Fix in 2022.1.X
Votes
2
Found in
2021.2.0a9
2021.2.1f1
2022.1.0a12
Issue ID
UUM-4117
Regression
Yes
Project Build Default Icon is not updating when changing icons and re-building
How to reproduce:
1. Open the user attached "yerp.zip" project
2. Go into File -> Build Settings -> Project Settings
3. Select the Player tab from the list
4. Set "1.jpg" as the Default Icon
5. Build the project from the Build Settings window
6. Navigate to the Build folder
7. Return to the Project Settings window
8. Replace "1.jpg" with "2.jpg" as the Default Icon
9. Build the project again from the Build Settings window
10. Navigate to the Build folder
Expected result: The Default Icon for the build is changing
Actual result: The Default Icon doesn't change
Reproducible with: 2021.2.0a9, 2021.2.1f1, 2022.1.a12
Not reproducible: 2019.4.31f1, 2020.3.20f1, 2021.1.25f1, 2021.2.0a8
Note:
- When changing the Default Icon through the Select button, the ".jpg" files may not appear
- To change the Default Icon, just drag and drop the ".jpg" files from the Assets folder
Comments (3)
-
syphase
Sep 14, 2023 05:16
Same issue here on 2021.3.9f1
-
Infos2
Jul 21, 2023 14:38
Facing the same issue 2 years later. Unity 2020.3.47f1
-
KickBack
Jun 17, 2023 02:26
This still happens by the way with 2021 LTS
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
Resolution Note:
We were unable to reproduce this issue, and it has not been reported again in a year.
Resolution Note (2022.1.X):
We were unable to reproduce this issue, and it has not been reported again in a year.