Search Issue Tracker
By Design
Votes
0
Found in
2021.3.48f1
2022.3.57f1
6000.0.37f1
6000.1.0b5
6000.2.0a2
Issue ID
UUM-96999
Regression
No
Canvas buttons are no longer interactable when copy-pasting a Canvas GameObject with Buttons into a new Scene
Steps to reproduce:
1. Open the attached “IN-93625.zip” project
2. Open the “Scene1”
3. In the Hierarchy Window, copy the “Canvas” GameObject
4. Open the “Scene2”
5. In the Hierarchy Window, paste the “Canvas” GameObject
6. Enter Play Mode
7. Press the button
8. Observe the results
Expected result: The button is interactable or a warning/error is thrown regarding a missing “EventSystem” GameObject
Actual result: The button is not interactable and no warnings/errors are thrown
Reproducible with: 2021.3.48f1, 2022.3.57f1, 6000.0.37f1, 6000.1.0b5, 6000.2.0a2
Reproducible on: Windows 11
Not reproducible on: No other environment tested
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
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
Resolution Note:
The new scene is missing an Event System component. This is what sends the events to the buttons.
Unity doesn't issue warnings for missing EventSystem components because it's designed to be flexible. Some scenes might intentionally omit an EventSystem (e.g., custom solutions, scenes without UI interaction, or shared EventSystem setups across multiple scenes). Adding a warning would risk false positives and disrupt workflows. There is also no good place to do a check for the EventSystem. Interactive elements are not aware of the EventSystem and should not be checking for it. This would come under a feature request.