mobile-debugging

Flipper is a desktop debugging platform that inspects React Native apps on connected devices or emulators. Launch your app, open Flipper, select your device, and use plugins to view logs, inspect the network layer, and monitor performance. It integrates with both iOS and Android without additional setup beyond installing the Flipper dependency.

Yes, network request debugging in Expo apps works through Flipper's network inspector or Chrome DevTools. Both tools intercept and display HTTP/HTTPS traffic, request headers, response payloads, and timing data. Flipper offers a more native experience on iOS and Android; Chrome DevTools works through remote debugging.

Crash analysis combines multiple tools: React DevTools and Chrome DevTools capture runtime errors and stack traces, Flipper displays native crash logs from iOS and Android, and error boundaries catch component failures before they crash the app. Use structured logging and crash reporting to correlate events leading to the crash.

Breakpoint management happens through Chrome DevTools remote debugging. Connect your device, open the debugger, set breakpoints in source files, and step through execution. React Native supports source maps for debugging transpiled code; pause execution to inspect variable state and call stacks.

Native module troubleshooting combines JavaScript-side debugging through React DevTools and Chrome DevTools with platform-specific tools. Use Xcode's debugger for iOS native code and Android Studio's debugger for Android. Flipper's native logs help surface errors from the native layer before they propagate to JavaScript.

Remote debugging workflows are supported on both iOS and Android through Chrome DevTools and Flipper. Chrome DevTools uses a network bridge for remote inspection; Flipper communicates directly with connected devices or emulators. Both approaches enable debugging without modifying your app's code.