Quick answer: Bind your actions to <Pointer>/press (covers Mouse + Touch + Pen) instead of <Mouse>/leftButton. Or add an explicit <Touchscreen>/primaryTouch/press binding alongside the mouse one.

A Unity mobile game uses the new Input System with a “Tap” action bound to <Mouse>/leftButton. The editor with mouse works perfectly. On Android device, taps register nothing. The phone’s touchscreen is treated as a separate device the action doesn’t bind.

The Pointer Abstraction

The Input System has a Pointer base class that Mouse, Touchscreen, and Pen all derive from. Bindings written against <Pointer> match any of them. Bindings against the concrete class only match that class.

Fix 1: Bind to Pointer

Open the .inputactions asset. For the Tap action:

Now Mouse left button, Touchscreen tap, and Pen tap all dispatch through this single binding.

Fix 2: Add Explicit Touchscreen Binding

If you need to keep Mouse-specific bindings (e.g., for right-click), add a second binding to the same action:

Both paths now dispatch to the same callback.

Fix 3: Enable Touch Simulation for Editor

For testing touch-only logic in the Editor without a device:

using UnityEngine.InputSystem.EnhancedTouch;

void OnEnable() {
    EnhancedTouchSupport.Enable();
    TouchSimulation.Enable();
}

Mouse clicks now also generate Touchscreen events. Tests Touchscreen-bound actions in the Editor without a phone.

Fix 4: Per-Touch Position

For multi-touch (pinch, etc.):

using UnityEngine.InputSystem.EnhancedTouch;

foreach (var touch in Touch.activeTouches)
{
    if (touch.began) DoSomething(touch.startScreenPosition);
}

EnhancedTouch.Touch.activeTouches gives you per-finger data, similar to legacy Input.touches. Cleaner than action bindings for multi-finger gestures.

Diagnosing

Open Window → Analysis → Input Debugger on the device or via remote debugger. Tap the screen — if Touchscreen events appear but your action doesn’t fire, the binding doesn’t include touch. Fix per above.

Verifying

Tap the screen on a real device. Your Tap callback should fire. Check the Input Debugger’s Listeners tab — the action should show Touchscreen as a valid source.

Understanding the issue

Input bugs are perceptible to players even when the gameplay code is correct. A 16ms delay that the profiler considers fine is the difference between 'responsive' and 'sluggish'. The fix is often in the input pipeline, not the gameplay.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

This bug class disproportionately affects late-stage development. The work to surface it is interactive testing in realistic conditions, which only really happens after the gameplay is in place and assets are populated. Catching it early requires deliberate testing of conditions that look unimportant.

At the engine level, the behavior comes from a deliberate design decision in Unity. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

Verifying this fix in isolation is straightforward: reproduce the bug, apply the change, confirm the bug no longer reproduces. The harder verification is regression - did this fix introduce a new bug elsewhere? Run your standard regression suite, plus any tests that exercise the same code path with different inputs.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

Related bug classes often share the same root cause. If you find yourself fixing this issue, look for cousins: similar symptoms in adjacent systems, the same data flow but a different value, or the same fix pattern in another module. The catalog of 'we've seen this before' becomes valuable institutional knowledge.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

For shipping titles with a long support window, watch for this issue resurfacing after dependency updates. Engine upgrades, driver updates, OS releases - each one can resurface a bug class you thought you'd fixed because the underlying behavior changed slightly. Regression tests catch the obvious ones; player reports catch the rest.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

If this issue manifests under high load (many actors, many particles, many network connections), profile the post-fix code path with realistic counts. The original cost was a bug; the new cost is real work, and real work has a budget.

Diagnostic approach

Before applying any fix, gather enough context to be confident you're addressing the actual cause and not a similar-looking symptom. The cheapest diagnostic step is reproducing the bug deterministically - if you can't get the same failure twice in a row, your fix attempts will be hard to evaluate. Lock down the reproduction first.

For Unity-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

Third-party plugins often provide better diagnostics for their own behavior than the engine does. If the affected code is in a plugin, check the plugin's documentation for debug modes, verbose logging, or inspector tools - these can save hours of investigation when they exist.

Within Unity, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Platform-specific edge cases are worth enumerating explicitly. iOS handles backgrounding differently than Android; Windows handles focus changes differently than macOS. A fix that works on the development platform may not work on every target. Test on each shipping platform deliberately.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

Document the fix and its rationale in the commit message or attached engineering doc. Future engineers will encounter related issues; the rationale tells them whether your fix is reusable or specific to the case at hand. Without rationale, the fix gets reverted or copied incorrectly.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“Mouse and Touchscreen are different devices. Use Pointer to cover both, or bind both explicitly.”

Default to <Pointer> bindings in any project that may ship to multiple platforms — saves rewiring later.