Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.2.X, 2019.3.X
Votes
0
Found in
2018.4.10f1
2019.2.7f2
2019.3.0b4
Issue ID
1185387
Regression
Yes
[VCS] Importing .unitypackage with version control enabled fails
Steps to reproduce:
1. Create new project in perforce workspace
2. In editor, connect to perforce server
3. Import 2D Game kit from asset store (when asked to update packages and checkout files - accept)
Actual result: None of the assets from package appear in the project - there's a "Failed to open one or more files for edit in Version Control" error printed to console and Importing Package progress bar doesn't disappear after the failure.
Reproduced with: 2018.4.10f1, 2019.2.7f2, 2019.3.0b4, 2020.1.0a5
Not reproducible: 2018.4.9f1, 2019.2.6f1, 2019.3.0b3
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
sfallier_scopely
Jun 04, 2021 22:49
I'm still getting this in Unity 2018.4.30f1 when trying to import the Google Play In-App Review package, version 1.4 (can be found on the google developers site)