workarounds.md

Compilation errors when importing

If you’re updating from the Asset Store, lingering files from an earlier installation may cause compilation errors. This happens because .unitypackage imports don’t clear old files from the folder.

When updating via GitHub patches, this is less likely, but still possible.

Solution:

1. Uninstall ASM completely before installing the newest Asset Store version.
2. Then install any patches for that version (patches are only guaranteed to work with the current Asset Store release).

Tip: You can also try right-clicking the AdvancedSceneManager folder and selecting Reimport.

Duplicate ASM packages in the project

In ASM 3.0 we renamed the package:

• 3.0: com.lazy-solutions.advanced-scene-manager
• 2.0: com.lazy.advanced-scene-manager

This could be another source of compilation errors, and if both appear in your project, you need to uninstall both before reinstalling 3.0.
This is necessary because Unity may mix asset IDs between versions, causing files to be split across the old and new folders.

Scene Manager Window not showing collections

After import (or when switching Git branches), ASM can sometimes get stuck in an unstable state where collections don’t appear.

Workaround: Reload the domain / recompile scripts. This usually restores stability.

Hint: You can force a recompile through ASM’s Dev Menu.
Right-click the menu button in the top-right corner of the ASM window and choose Recompile.

Scene loader not found error.

There are two common causes for this error:

• Missing dependency: Some scene loaders (such as the Addressables scene loader) are only available if the corresponding Unity package is installed. If a scene is configured to use one and the package is later removed, the loader can’t be found.
• Unstable state after import: Similar to the issue above, ASM may fail to initialize scene loaders properly after import or when switching Git branches. In this case, force a domain reload to restore stability.

“Ambiguous call” errors with Lazy.CoroutineUtility after upgrading ASM

ASM includes an embedded copy of Coroutine Utility.
If you also have the upm version of Coroutine Utility installed, Unity will report ambiguous call errors.

Fix: Remove the Coroutine Utility package from Package Manager so ASM will compile correctly.

ScriptableSingleton Errors During Build

You may occasionally see errors related to Unity’s ScriptableSingleton system when building your project. These typically appear in the Console during the build process and can look concerning at first glance.

In most cases, these errors are harmless and can be safely ignored. Unity may log these messages due to internal lifecycle quirks, especially when editor tools interact with serialized data, domain reloads, or build-time asset preparation. Even if errors are shown, the build itself often completes successfully and the resulting player works as expected.

What you should do

• If the build completes successfully, you can safely ignore these errors.
• If the build fails or stops, and the errors mention ScriptableSingleton, please try removing 'Assets/ASMBuild', if it exists, then restart. Otherwise, please report this to us along with the full error message.

Why this happens

These errors are typically caused by how Unity handles initialization and serialization of ScriptableSingleton instances during editor and build operations.

Future improvements

We are aware of these issues and plan to rewrite the settings system in a future update, which will remove reliance on ScriptableSingleton and eliminate these errors entirely.

Until then, as long as your build completes, these messages can be considered safe to ignore.

No scenes in build

This happens sometimes randomly, and will probably work on another attempt. This is due to the same issue as above with ScriptableSingleton.