Search Issue Tracker
Fixed in 3.0.0-pre.1
Votes
1
Found in [Package]
2.5.2
Issue ID
1310182
Regression
No
[Recorder] Serialized target has been destroyed error is thrown if undo is pressed after deleting any recorder
"Serialized target has been destroyed" error is thrown if undo is pressed after deleting any recorder. Refer the attached video
Steps to reproduce:
1) Create a new project
2) Window > Package Manager > Install Unity Recorder
3) Window > Package Manager > Install Mobile Notifications
4) Add any Recorder > Delete the recorder
5) Edit > Undo or Press Ctrl+Z
Actual result: "Serialized target has been destroyed" error is thrown in console
Expected result: No errors should be thrown in console
Occurring in: 2021.2.0a3, 2021.1.0b5, 2021.1.0a1, 2020.2.2f1, 2020.1.13f1, 2019.4.9f1
Environment: Both Windows and Mac
Stack Trace:
SerializedObject target has been destroyed.
UnityEngine.StackTraceUtility:ExtractStackTrace ()
Unity.Notifications.NotificationSettingsProvider:<Initialize>b__16_0 () (at Library/PackageCache/com.unity.mobile.notifications@1.3.2/Editor/NotificationSettingsProvider.cs:67)
UnityEditor.EditorApplication:Internal_CallGlobalEventHandler ()
Comments (1)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
vizgl
Aug 03, 2025 01:29
Still not fixed in the latest version [2.4.1]