Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
0
Found in
2019.4
2020.1
2020.2
Issue ID
1271116
Regression
No
Automatically add embedded package files to source control
When using the method `PackageManager.Client.Embed()` to embed a package in the project, or while embedding a package by dropping it in the Packages folder, no assets from the package are added to the source control sub-system.
Steps to reproduce:
1 - Open (or create) a Unity project
2 - Set up perforce version control
3 - Embed a package in the project (whether by dropping it on the Packages folder or through the api PackageManager.Client.Embed)
4 - Open P4V client and login with the same Workspace as the one used in step 2
Expected results: when embedding a package into a project its assets should be added into version control
Actual results: embedded package files are not added to source control
Comments (4)
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
malkovich90
Dec 16, 2020 10:03
Damm even I am having a similar kind of issue, I have searched all over the internet and even have posted on number of threads on different forum, no solution seems to work.