Search Issue Tracker
Fixed
Fixed in 2022.2.9f1, 2023.1.0b5, 2023.2.0a3
Votes
3
Found in
2022.2.5f1
2023.1.0b2
2023.2.0a1
Issue ID
UUM-25445
Regression
Yes
Script component no longer recognized in the Inspector when attached to a GameObject and then moved to a different location in the Project window
How to reproduce:
1. Create a new project
2. Create a new C# Script
3. Attach the C# Script to any GameObject in a Scene
4. Move the attached C# Script into the “Scenes” folder
5. Select the GameObject with the attached Script
6. Observe the Script Component
Expected result: The Script Component does not change in any way
Actual result: After recompilation, the Script Component is no longer recognized
Reproducible with: 2022.2.0a3, 2022.2.5f1, 2023.1.0b2
Not reproducible with: 2020.3.44f1, 2021.3.18f1, 2022.2.0a2
Reproduced on: macOS Ventura 13.1 (Intel), Windows 10
Notes:
- Workaround: Quit the project, delete the Library folder, and re-open the project
- If the “Scenes” folder does not exist, just create a new random one
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
- WebGL Player with WebGPU Graphics API fails to render Scene when custom Render Feature is used
- “EndLayoutGroup” error thrown when changing Shader Precision Model settings in Build Profiles window > Player Settings Overrides
- Button hover state uses default theme color when a custom .uss is applied
- Samples Showcase script warning does not clear after enabling required settings until GameObject is reselected
- VFX Particles receive shadow artifacts when using ShaderGraph with enabled shadows and Face Camera Plane Orient mode
AHambrick
Feb 09, 2023 22:40
I can confirm this behavior. Thank god for source control :)