Flutter, React Native & Unity

Inspect a React Native APK with Hermes: Bytecode Is Not Original Source

A React Native APK using Hermes can contain precompiled JavaScript bytecode rather than readable original JavaScript. Seeing that bytecode does not mean an analyzer can reconstruct the original source tree, comments or TypeScript types.

By Updated 2 min read

Verify the engine and bundle path

The Hermes documentation describes React Native's bundled engine and default use. It also warns that a custom bundle-loading path can use the engine without taking advantage of the intended precompiled bytecode.

Inspect release build configuration and actual packaged assets, not only a runtime engine flag.

Separate package layers

Layer What inspection can reveal
Android manifest Components, permissions and package metadata
Native libraries Engine and native-module architecture payloads
Hermes bundle Bytecode-level application material
Assets Images and other packaged resources

These layers do not restore the original project structure or development build configuration.

Preserve source maps for your releases

Keep the appropriate source maps and Android/native diagnostic artifacts associated with the exact build. JavaScript stack interpretation and native crash symbolization require different evidence.

Do not publish private source maps by default merely to make a crash report easier to read publicly.

Analyze only authorized artifacts

Use reverse engineering for your own app, a permitted audit or lawful interoperability work. Do not remove licensing checks or redistribute extracted proprietary assets.

A lost source repository is better recovered from backups, CI and source control than from compiled bytecode.

Use APKLint for inventory

The React Native APK Analyzer can help identify likely engine/bundle characteristics. The release guide remains the reference for producing a standalone artifact. APKLint cannot guarantee original-source recovery or prove runtime behavior from the bundle signature alone; validate conclusions against the build configuration and a controlled device test.

Sources and further reading

  1. React Native: Using Hermes
  2. React Native: Publishing to Google Play Store

Reference review: 22 September 2026. Examples illustrate the workflow; check your installed versions, release artifact and account-specific Console requirements before applying them. This guide is not a claim that APKLint executed your project or verified your private account.

APKLint

Android inspection tools and practical release guides. About APKLint · Report a correction