How to Fix Lost Controller Focus After Closing a Popup in Unity

After dismissing a confirmation popup with a gamepad, the menu becomes unnavigable because nothing is selected. The EventSystem's selection was destroyed with the popup. Here is how to fix it.

How to fix it

1. Save the prior selection

Before opening the popup, store EventSystem.current.currentSelectedGameObject so you know where focus should return.

2. Restore selection on close

When the popup closes, call EventSystem.current.SetSelectedGameObject(savedSelection) so the gamepad can navigate the menu again.

3. Fall back to a default

If the saved object is gone, select a sensible default control in the now-active screen so focus is never left null after the popup is destroyed.

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.