Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2019.3.0a7
2019.3.0a8
Issue ID
1166863
Regression
Yes
ScriptableSingleton already exists exception is thrown on removing 2d sprite Package
"ScriptableSingleton already exists. Did you query the singleton in a constructor?" exception is thrown on removing any Package.
Steps to repro:
1. Create a new Project.
2. Windows > Package Manager > 2D Sprite > Install.
3. Select 2D Sprite > Remove Package.
Actual Result:
ScriptableSingleton already exists exception is thrown on removing 2d Sprite Package.
Expected Result:
2D Sprite Package should be removed without any error in the console.
NOTE:
On installing 2D Sprite package "ReleaseAllScriptCaches did not release all script caches!" exception is thrown.
Reproducible in:
Unity Version: 2019.3.0a8 & Package Version: 1.0.0.
Working fine in:
Unity Version: 2019.3.0a7 & Package Version: 1.0.0,
Unity Version: 2019.2.0b8 & Package Version: 1.0.0.
Environment:
Only on Windows.
Stack trace:
ScriptableSingleton already exists. Did you query the singleton in a constructor?
UnityEditor.PackageManager.UI.AssetStore.AssetStoreOAuthInternal:.ctor()
Comments (4)
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
billw2011
Dec 30, 2020 22:46
Getting this all the time after installing a new package:
ScriptableSingleton already exists. Did you query the singleton in a constructor?
UnityEditor.PackageManager.UI.AssetStore.AssetStoreCacheInternal:.ctor()
kookyoo
Jun 03, 2020 09:13
Same here. We also use SteamVR and are still getting the error in 2019.3.15f1
pinkscooter
Apr 26, 2020 02:40
This happened to me when working with SteamVR in 2019.3.6f1
chriscode
Apr 24, 2020 21:42
HAd this the other day in 2019.3.10f1