Technique:Cross-platform app frameworks
Appearance
| On this wiki | Facts · Code · Notes · Topics |
|---|
Frameworks (Flutter, React Native with Hermes, Xamarin/.NET MAUI) that ship the app logic as a snapshot, bytecode or managed assemblies instead of Java/native code, so a native disassembler or a DEX decompiler sees only the runtime; how to recognise each in an APK and where the real code is.
Identification table (Android APK)
| Framework | Telltale files in the APK | Where the logic is | Page |
|---|---|---|---|
| Flutter | lib/<abi>/libflutter.so, lib/<abi>/libapp.so, assets/flutter_assets/ |
Dart AOT snapshot in libapp.so (debug builds: kernel_blob.bin in flutter_assets) |
Format:Dart AOT snapshot |
| React Native + Hermes | assets/index.android.bundle starting with C6 1F BC 03 C1 03 19 1F, Hermes VM library |
Hermes bytecode | Format:Hermes bytecode (HBC) |
| React Native + JavaScriptCore (older) | index.android.bundle is readable JS text, libjsc.so |
JavaScript text, sometimes minified | - |
| Xamarin / .NET MAUI | assemblies/ folder or lib/<abi>/libassemblies*.blob.so / libassembly-store.so, libmonodroid.so, libmonosgen-2.0.so |
.NET assemblies (IL), maybe XALZ-compressed | Format:Xamarin and .NET for Android assembly store |
| Java/Kotlin with R8 | classes*.dex with short names |
DEX, names obfuscated | Format:ProGuard and R8 mapping file, Format:DEX |
Use Format:APK to list the archive first (it is a ZIP), then pick the row.
General advice
- Do not spend time on the framework runtime (libflutter.so, libhermes, Mono): identify its version, then work on the app payload.
- The payload format is tied to a runtime version (Dart snapshot hash, Hermes bytecode version, store format version): find the version first, then pick matching tooling.
- Strings are often the cheapest entry: Hermes string table, Dart object pool strings, .NET #Strings/#US heaps, are all readable without full decompilation.
- iOS builds follow the same idea (App.framework for Flutter, main.jsbundle for Hermes); Unverified for details here.
See Platform:Android.
Managed code compiled ahead of time hides IL differently per toolchain: Format:.NET ReadyToRun keeps IL, Format:Mono AOT image keeps IL beside a native image, while Technique:Identifying .NET NativeAOT executables leaves no IL at all.