Search Issue Tracker
By Design
Under Consideration for 6000.0.X, 6000.1.X
Votes
0
Found in
6000.0.35f1
6000.1.0b3
Issue ID
UUM-95339
Regression
Yes
MissingComponentException not being thrown when inside an Awaitable
Reproduction steps:
1. Open the attached project ("AwaitableBug")
2. Open scene "Scenes/SampleScene"
3. In the Scene Hierarchy, select the "NullRef" GameObject
4. Uncheck "Await Version" and enter Play mode, notice that an exception is thrown in the console
5. Exit Play mode, check "Await Version" and enter Play mode again
Expected result: An exception is thrown, informing the user that a script is trying to access a non-existant component
Actual result: No exception is thrown
Reproducible with: 6000.0.0f1, 6000.0.35f1, 6000.1.0b3
Not reproducible with: 6000.0.0b15
Couldn't test with: 2022.3.56f1 (Awaitable is not available on this version)
Reproducible on: Windows 10 (User), macOS 15.1.1 (Intel)
Not reproducible on: No other environment tested
Note:
6000.0.0b15 and lower a Warning is thrown:
"Missing types referenced from component UniversalRenderPipelineGlobalSettings on game object UniversalRenderPipelineGlobalSettings"
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
- Crash on RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
- Scene view has Y coordinates of the Screen Position node flipped when some of the URP features are disabled
- Volumetric fog shader variants are missing from build when "Strict Shader Variant Matching" is disabled
- Unnecessary modifications clutter the Scene when using a RectTransform driven by a LayoutGroup in a Prefab
Resolution Note:
I looked at it, and this is by design: an awaitable captures and rethrows its exceptions when it is continued. As there is no awaiter waiting on the Awaitable object, the exception is never re-thrown.