Search Issue Tracker
Fixed in 2023.2.0a8
Fixed in 2023.1.X, 2023.2.X
Votes
0
Found in
2023.1.0a26
2023.1.0b1
Issue ID
UUM-25904
Regression
Yes
Asset isn't able to be completely removed from project
Steps to repo:
- Open a HDRP/URP/Core scene in Unity Editor
- Open package manager
- Import the "Feel" Asset
- In the Package manager click remove after the asset is in the scene
- Observe the console
Expected results: Asset is removed from project without issues
Actual results: Error in console
Issue first introduced in: 2023.1.0b1
Reproducible with: 2023.1.0a26, 2023.1.0b1
Not reproducible with: 2023.1.0a25
Tested on: Windows 11
Notes:
Asset link:
[https://assetstore.unity.com/packages/tools/particles-effects/feel-183370#reviews]
Error:
[Package Manager Window] Failed to remove the following asset(s) and/or folder(s):
Assets/Feel/NiceVibrations/Plugins/Windows/x64/nice_vibrations_editor_plugin.dll
Assets/Feel/NiceVibrations/Plugins/Windows/x64
Assets/Feel/NiceVibrations/Plugins/Windows
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)
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
- Camera.allCameras returns cameras from all loaded Scenes when using multi-Scene setup
- Camera.layerCullDistances has no effect when GPU Resident Drawer is enabled
- ARM64 and ARMv7 APKs return the same version code when "Split APKs by target architecture" is enabled
- Crash on ProfilerMutexLock when closing a project with specific Assets
- “Callback unregistration failed. Callback not registered.” is thrown when changing layouts with two "Font Asset Creator" windows docked
Resolution Note (fix version 2023.2):
Fixed in 2023.2.0a8