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
Comments (1)
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
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)