Search Issue Tracker
Fixed
Fixed in 2022.3.64f1, 6000.0.51f1, 6000.1.7f1, 6000.2.0b5, 6000.3.0a1
Votes
1
Found in
2022.3.60f1
6000.0.42f1
6000.1.0b10
6000.2.0a6
6000.3.0a1
Issue ID
UUM-100078
Regression
No
Assets do not get imported from an asset package when Library assets in the asset package are unchanged
How to reproduce:
1. Open the attached “IN-95957” project
2. Right click in the Assets folder in the Project window and create a new prefab named “GameObject” (Create → Scene → Prefab)
3. In the Toolbar select Test → Create Package
4. In the Project window right click on the Assets folder and select the Refresh option
5. Delete the “GameObject” prefab from the Assets folder
6. In the Project window Assets folder double click on the “Test Package” asset package
7. In the pop-up window select Import
8. In the “Import Unity Package” window click on Next
9. Observe the Assets folder in the Project window
Expected result: The “GameObject.prefab” asset gets imported from the asset package
Actual result: The “GameObject.prefab” asset does not get imported
Reproducible with: 2022.3.60f1, 6000.0.42f1, 6000.1.0b10, 6000.2.0a6
Reproduced on: Windows 10(User), Windows 11
Not reproduced on: No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Memory leak occurs when focused on Player while using Direct3D12
- 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
Add comment