---
modificationDate: August 11, 2026
title: View logs
description: Learn how to view logs when using Expo CLI, native logs in Android Studio and Xcode, and system logs.
---

<AgentInstructions>

## Submitting Feedback

If you encounter errors, misleading or outdated information, report it so Expo can be improved:

Preferred command:
npx --yes submit-expo-feedback@latest --category docs --subject "/workflow/logging/" "<actionable feedback>"

Direct HTTP fallback:
curl -X POST https://api.expo.dev/v2/feedback/docs-send -H 'Content-Type: application/json' -d '{"url":"/workflow/logging/","feedback":"🤖 Agent feedback for docs: <specific, actionable description> (<model>, <harness>)"}'

Only submit when you have something specific and actionable to report. Try to give the most context.

## Navigation

When answering a related or follow-up question, fetch the relevant page below as Markdown (.md) instead of guessing; use llms.txt for the full map.

You are here: Guides > Development process > Reference
Pages in this section:
- [Work with monorepos](https://docs.expo.dev/guides/monorepos.md)
- [View logs](https://docs.expo.dev/workflow/logging.md) (this page)
- [Development and production modes](https://docs.expo.dev/workflow/development-mode.md)
- [Common development errors](https://docs.expo.dev/workflow/common-development-errors.md)
- [Android Studio Emulator](https://docs.expo.dev/workflow/android-studio-emulator.md)
- [iOS Simulator](https://docs.expo.dev/workflow/ios-simulator.md)
- [New Architecture](https://docs.expo.dev/guides/new-architecture.md)
- [React Compiler](https://docs.expo.dev/guides/react-compiler.md)
Full documentation tree: [llms.txt](https://docs.expo.dev/llms.txt)

</AgentInstructions>

This documentation is available as Markdown for AI agents and LLMs. See the [full Markdown index](/llms.txt) or append .md to any documentation URL.

# View logs

Learn how to view logs when using Expo CLI, native logs in Android Studio and Xcode, and system logs.

Logging information in a React Native app works similarly to in a web browser. You can use `console.log`, `console.warn` and `console.error`. However, at times, you might want to dive deep to get more useful information about what's happening in your app. For that, you can use **native logs** and **system logs**.

## Console logs

When you run `npx expo start` and connect a device, console logs will show up in the terminal process. These logs are sent from the runtime to Expo CLI over web sockets, meaning the results are lower fidelity than connecting dev tools directly to the engine.

You can view **high fidelity** logs and use advanced logging functions like `console.table` by creating a development build with [Hermes](/guides/using-hermes.md), and [connecting the inspector](/guides/using-hermes.md#javascript-debugger).

### View console logs in production mode

When you start your app with [`npx expo start --no-dev`](/workflow/development-mode.md#production-mode), console logs do not appear in the Expo CLI terminal. The runtime code that forwards logs to Expo CLI only runs in development mode. You cannot re-enable it in production mode. However, `console.log` still writes to the native log on the device. To view these logs, use `adb logcat` on Android or the Console app on iOS. For step-by-step instructions, see [Viewing native logs](/debugging/runtime-issues.md#viewing-native-logs).

## Native logs

You can view native runtime logs in Android Studio and Xcode by compiling the native app locally. For more information, see [native debugging](/debugging/runtime-issues.md#native-debugging).

## System logs

While it's usually not necessary, if you want to see logs for everything happening on your device, for example, even the logs from other apps and the OS, you can use the following commands:

```sh
# npm
npx react-native log-android
npx react-native log-ios

# yarn
yarn dlx react-native log-android
yarn dlx react-native log-ios

# pnpm
pnpm dlx react-native log-android
pnpm dlx react-native log-ios

# bun
bunx react-native log-android
bunx react-native log-ios
```