Search Issue Tracker
Fixed in 5.3.0
Votes
2
Found in
5.0.0b21
Issue ID
668098
Regression
No
[Packages] Updated files from a package are not overwritten
How to reproduce:
1. Open attached project
2. Import the UpdatedPackage.unitypackage package into the project
- Note how the files are imported, but with an added number at the end
This behaviour is not optimal if packages are used for updating something.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
shadiradio
Sep 14, 2015 20:26
This still sadly occurs in 5.2, and it's one of the most frustrating things. Does anyone have any information on which version this is supposed to be fixed for?
TomNCatz
May 28, 2015 17:56
This issue seems to be related to #652856 which is listed as resolved in a future version. Does anyone know what version this is resolved in and how?
TomNCatz
May 28, 2015 17:42
if the functionality is as EXCLAMATIONMAREK describes then most serious package development will be halted. If you have binaries or anything else that needs to be edited externally for your plugin it will loose it's GUID and no longer properly update. My team has also run into SVN issued where the GUID is occasionally lost, making team development of a package unreliable.
If not the suggestion offered by EXCLAMATIONMAREK could we get some way of manually linking the old GUIDs to the new or some such so that we can continue developement?
ExclamationMarek
Mar 30, 2015 17:42
Noticed the same thing, but this only happens when the GUID of the files are different. The .unitypackage will store GUIDs of objects, so if each version of the package is made sequentially and applied to the same project, you should be fine. But if at any point you loose your meta files, or import the contents of the package to your project *not* from the package they may get different GUID, and getting an updated package will create the issue you described.
With that said, if would be really nice if upon importing, there was an "Override GUID" option, which would overwrite the current files, and assign the same GUIDs to the ones in the package.