UUM-56526
Fixed in 6000.5.0a7Mentioned in 16 release notes.
First fixed in 6000.5.0a7 (Feb 19, 2026); relisted in 15 later releases.
| Version | Section | Risk | Impact | Note |
|---|---|---|---|---|
| 6000.5.0f1 | Fixes Services | Fix | Fixed issue where native crash reports could be sent even after CrashReportHandler.enableCaptureExceptions = false at runtime on iOS, MacOS and Windows. | |
| 6000.5.0b11 | Fixes Services | Fix | Fixed issue where native crash reports could be sent even after CrashReportHandler.enableCaptureExceptions = false at runtime on iOS, MacOS and Windows. | |
| 6000.5.0b10 | Fixes Services | Fix | Fixed issue where native crash reports could be sent even after CrashReportHandler.enableCaptureExceptions = false at runtime on iOS, MacOS and Windows. | |
| 6000.5.0b9 | Fixes Services | Fix | Fixed issue where native crash reports could be sent even after CrashReportHandler.enableCaptureExceptions = false at runtime on iOS, MacOS and Windows. | |
| 6000.5.0b8 | Fixes Services | Fix | Fixed issue where native crash reports could be sent even after CrashReportHandler.enableCaptureExceptions = false at runtime on iOS, MacOS and Windows. | |
| 6000.5.0b7 | Fixes Services | Fix | Fixed issue where native crash reports could be sent even after CrashReportHandler.enableCaptureExceptions = false at runtime on iOS, MacOS and Windows. | |
| 6000.5.0b6 | Fixes Services | Fix | Fixed issue where native crash reports could be sent even after CrashReportHandler.enableCaptureExceptions = false at runtime on iOS, MacOS and Windows. | |
| 6000.5.0b5 | Fixes Services | Fix | Fixed issue where native crash reports could be sent even after CrashReportHandler.enableCaptureExceptions = false at runtime on iOS, MacOS and Windows. | |
| 6000.5.0b4 | Fixes Services | Fix | Fixed issue where native crash reports could be sent even after CrashReportHandler.enableCaptureExceptions = false at runtime on iOS, MacOS and Windows. | |
| 6000.5.0b3 | Fixes Services | Fix | Fixed issue where native crash reports could be sent even after CrashReportHandler.enableCaptureExceptions = false at runtime on iOS, MacOS and Windows. | |
| 6000.5.0b2 | Fixes Services | Fix | Fixed issue where native crash reports could be sent even after CrashReportHandler.enableCaptureExceptions = false at runtime on iOS, MacOS and Windows. | |
| 6000.5.0b1 | Fixes Services | Fix | Fixed issue where native crash reports could be sent even after CrashReportHandler.enableCaptureExceptions = false at runtime on iOS, MacOS and Windows. | |
| 6000.5.0a9 | Fixes Services | Fix | Fixed issue where native crash reports could be sent even after CrashReportHandler.enableCaptureExceptions = false at runtime on iOS, MacOS and Windows. | |
| 6000.5.0a8 | Fixes Services | Fix | Fixed issue where native crash reports could be sent even after CrashReportHandler.enableCaptureExceptions = false at runtime on iOS, MacOS and Windows. | |
| 6000.5.0a7 | Fixes Services | Fix | Fixed issue where native crash reports could be sent even after CrashReportHandler.enableCaptureExceptions = false at runtime on iOS, MacOS and Windows. | |
| 6000.5.0a7 | Fixes Services | Fix | Fixed issue where native crash reports could be sent even after CrashReportHandler.enableCaptureExceptions = false at runtime on iOS, MacOS and Windows. |