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
- 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
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
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.