# Resolve React Native debugging issues

Mobile issues can span Metro, native tooling, emulators, and application code. This skill provides structured checks and targeted commands for React Native and Expo debugging.

## Install

```bash
npx skillstore add babakbar/mobile-debugging
```

## Metadata

- Status: approved
- Slug: babakbar-mobile-debugging
- Skillstore revision: r3
- Version status: missing
- Tree hash: 58e473b24bcfddc54fc5746d6211e815028296cc0c254427a32b0417354ee7a3
- Author: BabakBar
- GitHub username: BabakBar
- License: MIT
- Repository: https://github.com/BabakBar/VibeKeeper/tree/main/.claude/skills/debugging
- Ref: 80999bf530a7874d7bedf8ce202001ecb4c4f5e0
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, filesystem
- Quality score: 75
- Public page: https://skillstore.pages.dev/skills/babakbar-mobile-debugging
- Manifest: https://skillstore.pages.dev/api/skills/babakbar-mobile-debugging/manifest

## Capabilities

- Suggest cache-reset steps for Metro bundler failures.
- Guide investigation of iOS pods, Android builds, and Expo prebuild issues.
- Identify commands for viewing iOS and Android device logs.
- Provide a React hook example for identifying slow component renders.
- Explain common JavaScript, native, dependency, and network error patterns.
- Provide a repeatable checklist for reproducing mobile application failures.

## Use Cases

- Restore a failing Metro build: Clear relevant caches and check dependencies when the bundler cannot resolve modules.
- Investigate device-only crashes: Collect iOS or Android logs and compare native error details with recent changes.
- Find rendering regressions: Add focused render-time logging to identify components exceeding a frame budget.

## Prompt Templates

### Start a Metro investigation

```
My React Native app cannot resolve a module. Give me the safest Metro troubleshooting steps and explain which commands change files.
```

### Review a native build error

```
My Android React Native build fails after adding a native module. Help me interpret the error and propose checks before cleaning build artifacts.
```

### Analyze slow rendering

```
My Expo screen feels slow. Show how to measure render duration, identify likely rerender causes, and propose a validation plan.
```

### Create a cross-platform debug plan

```
Create a step-by-step plan to diagnose a crash that occurs only on Android release builds. Include logs to collect, hypotheses, and safe rollback steps.
```

## Limitations

- It does not execute commands or inspect an application unless the host agent is given access.
- It does not diagnose proprietary crash reports without supplied logs and context.
- Some commands can remove local caches, build artifacts, simulator data, or processes.
- It focuses on React Native and Expo rather than native-only mobile applications.

## Best Practices

- Reproduce the issue and save the full error before running cleanup commands.
- Confirm the target project, device, port, and data scope before executing destructive commands.
- Change one variable at a time and verify the result after each step.

## Anti Patterns

- Do not delete simulator data or project dependencies before collecting error details.
- Do not use forceful process termination without confirming the process and port.
- Do not treat device logs as complete evidence without checking build type and environment.

## Security Audit

- Audited at: 2026-07-18T10:15:34.157\+00:00
- Summary: The skill is a React Native and Expo troubleshooting guide with no evidence of prompt injection, covert data collection, or unauthorized network activity. Several documented commands can delete caches or simulator data, alter builds, install packages, or terminate processes; users should review them before execution.

## Stats

- Views: 247
- Downloads: 10
- Favorites: 0
- Popularity score: 0