Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
0
Found in
2019.3.13f1
2020.1.0b9
2020.2.0a11
2020.2.0a13
Issue ID
1250933
Regression
Yes
Temp/Package files are added to VCS after installing any package and having Automatic Add on
How to reproduce:
1. Create a new project in your preferred workspace and open it
2. Connect it to Perforce and submit the initial project
3. Add any package to the project
4. Observe the VCS Window (Usually it doesn't update right away so you might need to press the refresh button)
Expected result: only the manifest.json file is checked out after adding packages
Actual result: the Editor tries to add all kinds of temporary files from the recently added package
Reproduced in: 2020.2.0a13, 2020.2.0a11, 2020.1.0b11, 2020.1.0b9, 2019.3.15f1, 2019.3.14f1
Not reproducible in: 2020.2.0a10, 2020.1.0b8, 2019.3.13f1, 2018.4.23f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment