Search Issue Tracker
Won't Fix
Votes
0
Found in
3.0.0b7
Issue ID
372710
Regression
No
Importing packages that have the same folder but different content fails (GUID issue)
Repro:
1) Import PackageOne.unitypackage
2) Import PackageTwo.unitypackage
Result:
The second package import reports that there's nothing new to import. This is not true:
Package1 contains: Editor/FileNumberOne.cs
Package2 contains: Edtior/FileNumberTwo.cs
Update: This is only reproducible by creating packages from files that have the same GUID. The repro steps below are what needs to be done to reproduce the packages already included with the case.
1) Create a package from a script file
2) Rename the script file and change some of it's content
3) Create a new package from the script file
4) Delete the packages
5) Import package1
6) Import package2
Result: Unity will tell you that it wants to import the file contained in package1 even though you're importing from package2. After import, you will only have one file. It will have the name of the script in package1 and the contents of the file in package2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment