Search Issue Tracker
By Design
Votes
0
Found in
2022.2.0a3
Issue ID
1398951
Regression
No
Different behavior when importing AssetStore package second time to the project
There are at least 4 different behaviors when you try to import AssetStore package second time to your project. Other than they are different, one of them have an issue. I am adding 4 comment to this case with explanation of each behavior
How can we reproduce it
1 Create new 3D Project
2 In browser open AssetStore package you want to download and press "Open in Unity"
3 This should open the package in PackageManager in Editor
4 Download and Import it
5 When it is done - try to import that same package again
Actual Results: behavior is different based on the package you selected
Expected Results: ideally behavior should be always the same - window saying "Nothing to import"
Reproduces and the same with: 2022.1.0b5, 2022.2.0a3
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
All that is kind of "by design", there will be a huge refactor of .unitypackage feature in the future which will improve the user experience a lot