DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to debug an app error from combined native and JS logs with Codex Mobile Dev Plugin

Read iOS, Android, and Metro logs together and send a failing stack trace to Codex.

Who it is forA developer whose app shows a crash or runtime error and who needs the native and JavaScript side of the failure in one place.

The problemNative logs, Android logcat, and Metro console output are usually in separate tools, so tracing one error across them takes time.

The outcomeCodex receives the error and its stack trace from the logs and proposes a fix grounded in the actual failure.

What you need first

  • Codex desktop on an Apple Silicon Mac
  • Xcode 26 or later with a simulator runtime for iOS simulators
  • Android SDK platform-tools and emulator, with an AVD or an authorized physical device, for Android
  • GitHub read access and working Git authentication while the repository is private
  • An existing local Metro server for Metro logs and React Native inspection

Steps

  1. Open Logs in Mobile Dev for the selected device.
  2. Follow the foreground app and use search or filters to narrow to the error.
  3. Send the error and its stack trace to chat.
  4. Ask Codex to explain the cause and propose a fix in your project.

Prompt for your agent

Using the callstackincubator/codex-mobile-dev-plugin Mobile Dev plugin, read the logs for the foreground app on <device name> and find the error matching <error text>. Expected output: a summary of the error with its stack trace and a proposed fix in <project path>. Verify the stack trace quoted matches the log entry before editing any file.

Caveat. Metro logs need an existing local Metro server, so the JavaScript side is only available when Metro is running.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page