Search Issue Tracker
Fixed
Fixed in 6000.6.0a2
Fix In Review for 6000.5.0b6
Under Consideration for 2022.3.X, 6000.0.X, 6000.3.X, 6000.4.X
Votes
0
Found in
2022.3.74f1
6000.0.68f1
6000.3.11f1
6000.4.0b11
6000.5.0a7
6000.6.0a2
Issue ID
UUM-136672
Regression
No
Diagnostics does not report Editor exceptions when using CrashReportingSettings.captureEditorExceptions
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “SampleScene“ Scene
3. In Diagnostics settings make sure project is connected to an organization (Edit > Project Settings > Services > Diagnostics)
4. Enter the Play Mode
5. Open https://dashboard.unity.com/
6. In Dashboard, select project
7. Click “View Diagnostics“
Expected result: Exception "editor2" is visible in Issues
Actual result: No Issues are present
Reproducible with: 6000.0.68f1, 6000.3.11f1, 6000.4.0b12, 6000.5.0a7
Reproducible on:
Play Mode
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Notes:
- After installing Cloud Diagnostic package and launching again - the Error is present in old Cloud Diagnostics
- When CrashReportingSettings is removed in “NewMonoBehaviour.cs“ Script and Windows Standalone Player with Mono is running, the exception is present in new Diagnostics
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
- Selected scenario changes when using the Save shortcut in the Configure Play Mode Scenarios window
- Unable to deselect variables in Graph Toolkit when clicking below or above the element
- "Duplicate item named ... encountered while searching the Item Library" warning persists after renaming the variables in Graph Toolkit
- Video Player preview stutters/lags when played in the Inspector preview during Play mode
- Camera frustum does not update in the Scene view when Output Texture referenced Render Texture is resized
Resolution Note:
Fixed in 6000.6.0a2
Resolution Note (fix version 6000.6.0a2):
Fixed in 6000.6.0a2
Resolution Note (fix version 6000.5.0b6):
Fixed in 6000.5.0b6