Search Issue Tracker
By Design
By Design in 6000.5.X
Under Consideration for 6000.4.X
Votes
0
Found in
6000.0.54f1
6000.2.15f1
6000.3.2f1
6000.4.0b1
6000.5.0a3
Issue ID
UUM-130245
Regression
No
“InvalidOperationException” errors are spammed in the Console when entering Play Mode in various TMP Sample Scenes
Steps to reproduce:
1. Create new Unity project
2. In Hierarchy create “Button - TextMeshPro” GO
3. In TMP Importer window select “Import TMP Essentials” button
4. In the same TMP Importer window select “Import TMP Examples & Extras”
5. Open “18 - ScrollRect & Masking & Layouts”
6. Enter Play Mode
7. Observe Console window
\\
Actual results: “InvalidOperationException: You are trying to read Input using the UnityEngine.Input class, but you have switched active Input handling to Input System package in Player Settings.” Warnings are spammed in the Console window when entering Play mode
Expected results: No errors present the Console window
\\
Reproducible with versions: 6000.0.54f1, 6000.2.15f1, 6000.3.2f1, 6000.4.0b1, 6000.5.0a3
\\
Tested on (OS): Ubuntu 24.04, macOS Tahoe 26.1 (M1)
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Active Targets section text in Graph Inspector is truncated despite available space
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- Module installation fails with "Download failed: Validation Failed" errors when using beta.2 Hub version
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.
These errors occur as a result of loading a scene that contains an EventSystem that is configured to use the legacy input system when the project itself is configured to use the new Input System package with the Player Settings - Active Input Handling set to exclusively use the new Input System.
Clicking on any of these errors brings up the EventSystem in the Inspector, revealing a message that informs the user of the source of these errors and option to resolve this. This behavior is by design and not related to TextMesh Pro but instead related to the EventSystem and input systems.
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.5.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.
These errors occur as a result of loading a scene that contains an EventSystem that is configured to use the legacy input system when the project itself is configured to use the new Input System package with the Player Settings - Active Input Handling set to exclusively use the new Input System.
Clicking on any of these errors brings up the EventSystem in the Inspector, revealing a message that informs the user of the source of these errors and option to resolve this. This behavior is by design and not related to TextMesh Pro but instead related to the EventSystem and input systems.
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.