 This issue occurs due to the incorrect usage of ScriptableSingleton. A fix is planned for a future update.