# Error handling in a chromeless UI on Android

A chromeless UI must present its own error state because the SDK does not render controls or viewer-facing error messages for you.

Decide how to present recoverable and terminal failures, whether viewers can retry, and which details should be retained for diagnostics. Clear loading indicators when an error occurs so the interface does not appear to buffer indefinitely.

See the [Android error-handling guides](https://docs-preview.optiview.dolby.com/pr-873/theoplayer/how-to-guides/android/miscellaneous/error/introduction.md) to detect Player errors and map them to messages and recovery actions.