Quick answer: On selection change, compute the selected item's position inside the content and set the ScrollRect's normalized position so the item is brought into view.

Scrolling a long settings or inventory list with a gamepad lets the highlight disappear below the fold because the view never follows. The viewport ignores focus. Here is how to fix it.

How to fix it

1. Detect selection changes

Hook each item's OnSelect (from ISelectHandler) or poll the EventSystem so you know when the focused item changes.

2. Scroll the item into view

Convert the item's anchored position to a normalized scroll value and assign it to scrollRect.verticalNormalizedPosition so the selected row is visible within the viewport.

3. Add padding so edges are reachable

Offset the scroll target slightly so the top and bottom items are not flush against the mask edge, which makes the focused row readable.

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.

The bug you can't reproduce isn't gone — it's just invisible until you capture it from the player's device.