01-apk-edition-analyzer

Decompile the APK with apktool and jadx, then grep the manifest, smali files, and resources.arsc for known ad network signatures such as com.google.android.gms.ads, com.applovin, and com.unity3d.ads. Each detection should record the file path and caller method as evidence.

Search the decompiled smali code for BuildConfig fields, FLAVOR, IS_PREMIUM, isPro, and BillingClient references. Record the field name, default value, and the gating branch opcodes like if-eqz or if-nez that control premium access.

Yes. XAPK files are extracted first, split config APKs and obb assets are listed, and the primary base.apk is selected for deep decompilation while the split layout is recorded in the output.

Google Sign-In fails with ApiException 10 unless the new keystore SHA-1 is added to Firebase Console. Self-signature checks, Play Integrity, SafetyNet, and Firebase App Check can also detect the signature change and block the app.

No. The analyzer is strictly read-only and does not modify, patch, rebuild, or re-sign the package. It only produces analysis.json and REPORT.md so a separate downstream converter can act on the findings.

Obfuscation is assessed by checking for shortened class hierarchies like smali/a/b/c.smali and apktool.yml framework markers. The result is classified as none, light, or heavy, and class names are never guessed on obfuscated code.