Diagnose React Native and Expo issues with Bash, Read, and Grep workflows.
npx skills add https://github.com/BabakBar/VibeKeeper --skill mobile-debugging
Please help me install this Agent Skill. Skill: Mobile Debugging Source: https://github.com/BabakBar/VibeKeeper/tree/main/.claude/skills/debugging Command: npx skills add https://github.com/BabakBar/VibeKeeper --skill mobile-debugging
Debugging React Native and Expo apps can be slow and fragmented due to scattered logs, platform-specific quirks, and flaky builds. This Skill provides a structured guide to diagnose Metro bundler errors, native module failures, performance issues, and crash analyses, helping you cut debugging time dramatically.
To start debugging, reproduce the issue and ask for a prioritized fix plan. Then run cache-clearing and log-check commands:
High-intent search queries and answers about installing and using this skill.
Metro bundler errors stem from cache corruption or stale dependencies. Clear caches with `npx expo start --clear` and `watchman watch-del-all`, then reinstall node_modules. Review Metro logs for specific failure points—syntax errors, missing modules, or circular dependencies—and fix the source before restarting the bundler.
Reproduce the crash consistently, then check logs from device or emulator using `npx react-native log-ios` or `npx react-native log-android`. Isolate whether the crash originates in JavaScript, native code, or a third-party module. Clear caches and reset native environments—pod deintegrate and adb shell pm clear—to rule out build artifacts before investigating the root cause.
Yes. Expo apps with native modules require pod installs on iOS and gradle syncs on Android. When native modules fail, run `pod deintegrate && pod install` in the ios folder and rebuild. Check native build logs for linking errors, missing frameworks, or version mismatches between the module and the native SDK.
Performance debugging involves profiling render performance, memory usage, and frame rates through device logs and Metro output. Use console logging to track slow component renders, then cross-reference with Metro bundler metrics and native memory reports. Network debugging helps isolate whether latency comes from JavaScript execution, bridge overhead, or backend calls.
Yes. Stale caches cause flaky builds and misleading logs. Always run `npx expo start --clear`, `watchman watch-del-all`, and `rm -rf node_modules && npm install` before a full rebuild. On Android, use `adb shell pm clear` to reset app state; on iOS, reset the pod environment with `pod deintegrate && pod install`.
Device and emulator logs capture native crashes, runtime errors, and system-level failures that Metro or console output miss. iOS logs expose framework errors and pod mismatches; Android logs show native module linker errors and ADB-level diagnostics. Unified log review across Metro, device, and console pinpoints whether the fault is in JavaScript, native code, or the bundler.
FutureAtomsGuide React Native Expo SDK 54 development builds and debugging with DevTools.
robertzengcnAutomate iOS bug fixing from source analysis to device verification.
msichtermanCreate and distribute Expo development clients for iOS and Android testing.
Axel-DaMageBuild and optimize React Native and Expo mobile applications for iOS and Android.
