Copyright © 2026 Unity Technologies
The "You are trying to read Input using the UnityEngine.Input class, but you have switched active Input handling to Input System package" error occurs because the active Web build profile has Active Input Handling set to Input System (New), while the global Player Settings has it set to Both. This build profile carries its own Player Settings, and those are authoritative when the profile is active — the global Player Settings value does not apply to Play mode or builds made with the Web profile active. On the attached project: Global Player Settings: Active Input Handling = Both (activeInputHandler = 2) "Web - Mobile - Release" build profile: Active Input Handling = Input System (activeInputHandler = 1) With the Web profile active, the runtime uses the profile's value (Input System only), which disables the legacy Input Manager. Any UnityEngine.Input call then throws the reported error. Changing Active Input Handling in the global Player Settings has no effect here, because the active profile's value takes precedence. This is a project configuration issue — not a data round-trip or migration problem. The profile stores a native player-settings subasset with activeInputHandler = 1 (no stale/legacy YAML involved). Set Active Input Handling to Both (or Input Manager Old) on the "Web - Mobile - Release" build profile itself. Play mode and builds made with that profile active will then keep the legacy Input Manager enabled, and the error will no longer occur.
How to Reproduce:
1. Open the attached “IN-148118” project
2. Go to File → Build Profiles and make sure that “Web” is the Active Build Profile
3. Go to Edit → Project Settings → Player → Web Settings
4. Under “Configuration” make sure that “Active Input Handling” is set to “Both”
4. Open “SampleScene”
5. Enter Play mode
6. Observe the console
Actual Result: Input Handling errors in the Console
Expected Result: No errors in the Console
Reproducible with: 6000.7.0a2, 6000.7.0a4
Not Reproducible with: 6000.0.0f1, 6000.0.80f1, 6000.3.20f1, 6000.5.5f1, 6000.6.0b5, 6000.7.0a1
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
Issues you vote on will appear here