Quick answer: Disable Has Exit Time for interrupt-driven transitions, or set a reachable exit time and add a parameter condition so the state can be left.

Your character gets locked in an attack or land state and ignores input. The transition relies on Has Exit Time but the looping clip never hits the exit moment as configured. Switching to a parameter-driven transition unsticks it.

How to fix it

1. Disable Has Exit Time for interrupts

For transitions that should happen on input or a condition, uncheck Has Exit Time so the Animator leaves the state as soon as the parameter condition is met.

2. Set a reachable exit time

If you do want timed exit, ensure Exit Time is within 0..1 of an actually-played, non-looping clip; on a looping clip an exit time greater than the played range never triggers.

3. Add a fallback parameter

Drive a trigger or bool that the transition also checks, so even if exit time misbehaves the state can be left when game logic requires it.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Unity error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

Reproduce it once with full context and the fix writes itself. The hunt is the expensive part.