Search Issue Tracker

Won't Fix

Won't Fix in 2023.1.X

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

Scripting

-

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

  1. 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;`

  2. Resolution Note (2023.1.X):

    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;`

Log in to vote on this issue

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues