Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.40f1
2021.3.10f1
2022.1.16f1
2022.2.0b7
2023.1.0a10
Issue ID
UUM-13914
Regression
No
UnityException is thrown when the affected code has no "isPlaying" method
How to reproduce:
1. Open the attached “IN-13813” project
2. Open the “Home” Scene
Expected result: No errors are thrown
Actual result: “UnityException: get_isPlaying is not allowed to be called from a MonoBehaviour constructor” is thrown
Reproducible with: 2020.3.40f1, 2021.3.10f1, 2022.1.16f1, 2022.2.0b7, 2023.1.0a10
Reproduced on: macOS Monterey 12.0.1
Note:
- If after step 2 no error is thrown, enter Play Mode
- User reported that this was a regression somewhere in the 2021.2 stream, but after testing it was reproducible
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
Issue with user code. The `GameStats.cs` has a static field initializer that gets an instance from the `Singleton<GameStats>.Instance` that calles `isPlaying`.
Simple workaround is to call `Singleton<GameStats>.Instance` directly or make it into a property like `public static GameStats Instance => Singleton<GameStats>.Instance;`