mobile-debugging

rozwer's avatarfrom rozwer

Use for React Native / Expo troubleshooting (Metro bundler, native modules, simulator/emulator issues).

⭐0stars🔀0forks📁View on GitHub🕐Updated Dec 29, 2025⬇️1downloads

When & Why to Use This Skill

This Claude skill is a specialized diagnostic assistant designed for React Native and Expo mobile development. It streamlines the troubleshooting process by providing structured workflows to resolve complex Metro bundler errors, native module conflicts in Xcode or Gradle, and environment-specific issues within simulators and emulators. By focusing on root-cause analysis and minimal-change interventions, it helps developers maintain a stable development environment and accelerate the debugging cycle for cross-platform mobile applications.

Use Cases

  • Metro Bundler Troubleshooting: Diagnosing and fixing JavaScript bundling errors, connection timeouts, or stale cache issues that prevent app loading.
  • Native Build Resolution: Identifying and resolving platform-specific build failures in Xcode (iOS) or Gradle (Android) related to native dependencies.
  • Environment & Simulator Setup: Debugging configuration mismatches or runtime exceptions occurring specifically on mobile simulators and emulators.
  • Dependency & SDK Alignment: Validating that project configurations, environment variables, and library versions are compatible with the chosen Expo or React Native workflow.
namemobile-debugging
descriptionUse for React Native / Expo troubleshooting (Metro bundler, native modules, simulator/emulator issues).

Workflow

  1. Capture the exact error and environment (RN/Expo version, platform, device).
  2. Separate concerns:
    • bundler issues (Metro)
    • native build issues (Xcode/Gradle)
    • runtime issues (permissions, network, JS exceptions)
  3. Reproduce with the smallest command set (e.g., one expo start / npx react-native run-*).
  4. Validate configuration files and dependencies align with the chosen workflow.
  5. Apply minimal change; re-run the exact failing path.

Common checks

  • Clear caches only after capturing logs (e.g., Metro/Gradle).
  • Confirm environment variables and platform-specific config are consistent.