Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2017.2.0b2
Issue ID
927152
Regression
No
[Perforce] Version Control window will trigger a connection loop if the connection settings are wrong
Steps to reproduce:
1. Set up Perforce server
2. Open Unity
3. in ProjectSettings -> Editor choose Perforce Version control and input the host, name and workspace info, except make sure the workspace is not a correct/existing one
4. Open Version Control window
5. Click on Incoming or Outgoing tabs
6. Console will be spammed with connection attempts
Expected: If connection is unable to complete, it should state why and stop trying
Actual: When connection is unable to be made, it keeps trying and spamming errors
Reproduced on 2017.2.0b2, 2017.1.0f2, 5.6.2p2, 5.5.4p1
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note (fix version 2019.3):
Fixed in: 2019.3.0a3