Our 'Debugging' tag archive includes a variety of articles and tutorials that provide insights into different debugging techniques and best practices.
View All TagsReact Native debugging changed a lot since Flipper was the default answer. In modern React Native apps, the first tool to open is React Native DevTools. Use native tooling from Xcode and Android Studio when you need to debug the platform layer, and keep Flipper only for older apps or custom plugin workflows that still depend on it.
Hermes is the JavaScript engine optimized for React Native. In modern React Native and Expo projects, Hermes is the default path for most apps, so the real question is no longer "How do I turn Hermes on?" It is "How do I confirm Hermes is working, benchmark the app properly, and avoid update/runtime mismatches?"
React Native tooling has changed. Older lists often recommended Flipper, Nuclide, standalone React Native Debugger, or remote Chrome debugging as the default workflow. Modern React Native apps should start with React Native DevTools, Metro, and the native tools that ship with Xcode and Android Studio.
Optional imports are useful when a React Native app has platform-specific code, feature-gated screens, optional assets, or native modules that should only load in one environment. They are also easy to misuse. Metro still needs to know what files can be bundled, so arbitrary runtime strings are not a good import strategy.
Debugging code written in Swift/Objective-C can be tricky sometimes, especially for someone who’s just starting to learn iOS programming. We’re listing a few techniques and tools for debugging code in Xcode, that any successful mobile app developer should be familiar with. The inspiration for this list was the work we’ve done building our beautiful iOS app templates.