Skip to content

Commit ef505e2

Browse files
authored
Update workarounds.md
1 parent 041007c commit ef505e2

1 file changed

Lines changed: 21 additions & 0 deletions

File tree

workarounds.md

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -43,3 +43,24 @@ ASM includes an embedded copy of **Coroutine Utility**.
4343
If you also have the upm version of Coroutine Utility installed, Unity will report ambiguous call errors.
4444

4545
**Fix:** Remove the Coroutine Utility package from Package Manager so ASM will compile correctly.
46+
47+
## ScriptableSingleton Errors During Build
48+
49+
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.
50+
51+
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.
52+
53+
### What you should do
54+
55+
- If the build **completes successfully**, you can safely ignore these errors.
56+
- If the build **fails or stops**, and the errors mention `ScriptableSingleton`, please report this to us along with the full error message.
57+
58+
### Why this happens
59+
60+
These errors are typically caused by how Unity handles initialization and serialization of `ScriptableSingleton` instances during editor and build operations.
61+
62+
### Future improvements
63+
64+
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.
65+
66+
Until then, as long as your build completes, these messages can be considered safe to ignore.

0 commit comments

Comments
 (0)