What causes UI cut off by the notch?

The UI extends into the display cutout and rounded corners because it ignores the safe-area insets the device reports, so buttons and text land under the notch or off the readable area.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix UI Cut Off by the Notch on Mobile

Quick answer: Read the platform safe-area insets and anchor important UI inside them, keeping interactive and critical elements out of the notch and corner regions.

UI hidden behind the notch is a safe-area problem: the game draws into regions the hardware obscures. Respecting the reported insets fixes it. Here is how.

How to fix it

1. Read the safe-area insets

Each platform reports the safe area (the usable region excluding notch, corners, and home indicator). Query it and use it to inset your UI canvas rather than assuming the full screen is usable.

2. Anchor critical UI inside the safe area

Place buttons, health bars, and text within the safe region. Background art can extend edge to edge, but anything the player must see or tap should stay inside the insets.

3. Test on devices with cutouts

Notches and indicators vary. Test on a few representative devices (and the simulator's safe-area overlays) so you catch UI that lands under a cutout on one phone but not another.

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 mobile 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.

Ship the fix, watch the signature disappear from the next build. That's how you know it's really gone.