Search Issue Tracker
By Design
By Design in 6000.6.X
Votes
0
Found in
6000.5.0a8
6000.6.0a1
Issue ID
UUM-135650
Regression
No
51 Compilation Errors (CS0246) in customization samples after removing Timeline package
Steps to reproduce:
- Create a Universal 3D project
- Open the Package Manager window (Window -> Package Management -> Package Manager)
- Find the "Timeline' package in the "Unity Registry"
- Select it
- Click "Manage -> Remove"
- Observe the Console view
Actual results: User gets 51 error "Assets/Samples/Timeline/1.8.9/Customization Samples/Annotation/AnnotationMarker.cs(9,6): error CS0246: The type or namespace name 'CustomStyle' could not be found (are you missing a using directive or an assembly reference?)" in the Console view
Expected results: No errors
Reproducible with versions: 6000.5.0a8
Not reproducible with versions: 6000.5.0a7
Tested on (OS): macOS - Tahoe 26.2
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
- InvalidCastException is thrown when hovering over a Tilemap with a saved Random Brush pick containing empty cells
- [VisionOS] Animating a material property results in artifacts when the app mode is set to RealityKit and shader modifies the Vertex Shader
- "DirectoryNotFoundException" is thrown and Shader Graph does not open when opening a .shadegraph from a long path
- "Undo: Already found nextRootTransform, but with different state cached" error thrown when undoing changes made to the Hierarchy using a script
- "No GUI Implemented" is displayed when using PhysicsMask with a CustomEditor
Resolution Note:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
Resolution Note (6000.6.X):
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.