One app can arrive in several files
An APK is an Android package. Split installations divide an app across a base package and extra packages for features, resources, or device targets. Archive formats can group those files together.
Preserve the package set from one app version. Mixing files from different versions gives the analysis a broken input.
Keep the original package
Upload the original file you received. Keep its filename, version, package name, and hash in your records. Avoid unpacking and repacking it just to change its extension.
For an archive, inspect the file list and identify the app members. A resource split and a base APK serve different roles.
Check coverage before drawing conclusions
A report should name the files it reviewed and the portions it could not read. Native libraries can exist in architecture splits rather than the base package.
“Not found” means little when the relevant member is missing. Use the coverage record to decide what needs another scan.
Recover only the unfinished work
A rescan can reuse completed results when the file identity, analyzer version, and stored results support that path. Changed inputs need fresh analysis for the changed parts.
Read the new coverage record after the scan. Saved findings and a failed stage can exist together; neither should hide the other.
How splits affect a finding
Android treats installed split APKs as one app with shared code and resources. Feature splits can contain code for a screen; configuration splits can hold device-specific resources. Review the member list before setting coverage.
When native libraries are missing from the base file, inspect the architecture splits. When a workflow uses a feature not covered in the package set, keep that gap explicit. A report can contain valid findings while still lacking the files needed for complete review.
Android’s bundle documentation explains the split mechanism and its role in app delivery. Keep that package model separate from archive naming: the files inside an archive determine what the analysis has to work with.
Give the project a clear target
After the app is uploaded, name the workflow and the client environment. The package format changes analysis inputs, not the result you want.
Keep access details private and send them through your project’s support flow.
Build what you need.
Upload your app. We extract its APIs and build your client.
Upload your app