Search Issue Tracker
Won't Fix
Won't Fix in 2.0.X
Votes
0
Found in [Package]
1.3.0
2.0.1-pre.18
Issue ID
DSTR-489
Regression
No
"LogAssert.NoUnexpectedReceived" does not catch exceptions when entering Play Mode
How to reproduce:
1. Open project "UnityTestException.zip"
2. Open Menu > Window > General > Test Runner
3. Select "NoExceptionEnterPlayMode" and press the "Run Selected" button
4. Observe the result
Expected result: Test fails
Actual result: Test passes
Reproducible with: 1.1.14 (2019.4.0f1), 1.1.31 (2019.4.38f1, 2020.3.33f1, 2021.3.1f1, 2022.1.0f1), 2.0.1-pre.18 (2022.2.0a11)
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
- Addressables.CheckForCatalogUpdates() always returns 0 when "Only update catalogs manually" is enabled
- VFX Graph forces a lengthy recompilation freeze when exiting Play Mode with a cloned Render Pipeline asset
- Project Auditor's "Install Rules" button has to be pressed twice to proceed when any compilation error in the Editor is present
- Crash on Scripting::UnityEngine::SubsystemManagerProxy::ClearSubsystems when adding a Mesh Collider Component to a GameObject
- ScrollView clips content when under an ancestor that has a filter set
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (2.0.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (2.0.X):
Won't do any 2.0 fixes, 2.0 is never going to be released