Search Issue Tracker
Fixed in 2021.1.X
Votes
0
Found in
2019.4
2020.2
2021.1
2021.2
Issue ID
1314073
Regression
No
Manually embedded packages are not added in Perforce
Reproduction steps:
1) Create a project.
2) Configure it to be tracked by Perforce and push it to Perforce. Verify that Automatic Add is enabled on Version Control.
3) Manually embed one package into the project from the project package cache without renaming the package folder.
4) Go back to Unity and trigger an automatic refresh (or do a manual one in case the automatic option is disabled).
5) Check on Perforce the status of the files from the just embedded package.
Expected Result:
Embedded packages files should show in Perforce as marked for Add.
Actual Result:
Embedded packages files show in Perforce they do not reside in depot.
Workaround:
- While manually copying the package folder from the cache, before triggering the refresh, rename the embedded package folder to just contain the package name, removing the version. For example `com.unity.2d.animation@5.0.3` should be renamed to `com.unity.2d.animation`
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Look Dev” window restored from previous HDRP project causes errors in newly created URP project
- Shader Variant creation window gets stretched out when canceling
- Validation message "Profile name is unsupported" is unclear and does not provide information on what is wrong
- Enabling Override Variant Limit toggle Warning Threshold value gets set to 8
- Missing space in Shader Graph project settings
Add comment