Search Issue Tracker
Fixed in 2.1.0-preview.6
Votes
0
Found in [Package]
2.1.0-preview.6
Issue ID
1403533
Regression
No
Unable to launch Editor with Perforce connection when launching with Editor CLI
How to reproduce:
1. Set up a Perforce Workspace with the Unity project inside it
2. Try to open the project with command line "<Path to Unity exe>\Unity.exe" -projectPath "<Project path>" -vcsMode Perforce -vcPerforceUsername <p4username> -vcPerforcePassword <p4password> -vcPerforceWorkspace <workspace> -vcPerforceServer <p4server>
Expected result: Project opens successfully
Actual result: Project fails to open
Reproducible with: 1.17.2, 2.1.0-preview.6 (2021.3.9f1, 2022.1.16f1, 2022.2.0b8, 2023.1.0a4
Not reproducible with: 1.17.2, 2.1.0-preview.6 (2023.1.0a5, 2023.1.0a9)
Could not test with: 2020.3.38f1 (Error: "The type or namespace name 'AddressableAssets' does not exist in the namespace 'UnityEditor' (are you missing an assembly reference?")
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
- NullReferenceException when setting 'isTextObjectScaleStatic' to false on a disabled TextMeshPro GameObject
- Shader Stripping Custom Options disappear when exiting Play mode without reloading Domain
- Decals do not get projected when 'Rendering Layer Mask' on a GameObject is 23rd Layer or above due to encoding/decoding issues
- Deriving from SearchContextAttribute doesn't always work
- Scripting API documentation is missing for macOS editor extensions
Resolution Note (fix version 2.1.0-preview.6):
Fixed in: 2.1.0-preview.6 (2023.1.0a5)