---
title: Native crash reporting in Expo's Observability service
authors: Kadi Kraman
published: October 7, 2026
---

Until now, the Errors page showed only what went wrong in your JavaScript. A crash in native code took the app down without a trace. Now `expo-observe` records those too, on both Android and iOS, with no setup. Update to 57.0.21 or later on SDK 57.

On Android, this covers uncaught Java and Kotlin exceptions, plus the crash records the operating system keeps for your app on Android 11 and later. On iOS, it covers Mach exceptions such as `EXC_BAD_ACCESS`, Unix signals such as `SIGSEGV`, and uncaught Objective-C and Swift exceptions.

Native crashes land in the same list as your JavaScript errors. Filter by source to see one or the other, and watch crash-free sessions for the overall picture. Open a crash to see its stack trace, the session records that led up to it, and a breakdown by app version, OS, device, and country.

Ready to fix it? Select **Hand off to AI** on the error details page to send the crash and its context straight to Claude Code or Codex.

![Hand off to AI example with an error](https://cdn.sanity.io/images/9r24npb8/production/06e1a4439667dcca9a97e10467424a04a8475790-2626x1912.png)

Error reporting is in preview. [Read the error reporting docs.](https://docs.expo.dev/eas/observe/errors/)