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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
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.