Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2019.3.0b12
2020.1.0a15
Issue ID
1202668
Regression
Yes
NullReference errors are continuously spammed when adding a package from disk and having version control mode set to 'Perforce'
How to reproduce:
1. Create a new project and open it
2. Go to Edit -> Project Settings -> Editor -> Version Control Mode dropdown, switch it to Perforce without entering any credentials
3. Open the Package manager and try to add the attached "LocalPackage" from disk
4. Observe the console errors
Expected result: no errors are spammed for the 2020.1.0a15+ versions and a simple warning/error is thrown describing why the manager can't add the package from disk (Because the version control is not properly connected yet and thus the manifest.json file is not writable. Something along the lines of: "Version control 'Perforce' is not connected; if you want to work without an active connection use 'Work Offline' option in editor settings")
Actual result: In the 2020.1.0a15+ versions a nullreference error is continuously spammed and on older than 2020.1.0a15 versions a nondescript error is thrown once
Reproduced in: 2020.1.0a15 (Nullreference errors are continuously spammed)
Not reproducible in: 2020.1.0a14, 2019.3.0f2, 2019.2.15f1, 2018.4.14f1 (No nullref spam but the error is undescript and could be improved)
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
- Nothing happens when entering a converter ID to target property in the Add Binding window when a converter ID was already added and removed
- Select Scriptable Object window freezes and becomes unresponsive when currently opened UXML Template is selected for binding's Data Source
- [Linux] “ReleaseButton expects buttonId >= 0” error is thrown when importing Assets via drag and drop
- [Linux] Numeric field value stops increasing when cursor reaches the edge of the monitor while dragging
- Asset gets unselected and added Subgraphs list item is not undone when performing Undo in Heatmap with Default Values asset Inspector
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.0a22