Read APK Information: Package Name, Version and SDK Levels

Extract the identity fields

The following Android SDK commands work without installing the application:

apkanalyzer manifest application-id app.apk
apkanalyzer manifest version-code app.apk
apkanalyzer manifest version-name app.apk
apkanalyzer manifest min-sdk app.apk
apkanalyzer manifest target-sdk app.apk

Use an explicit path to the SDK's apkanalyzer executable when it is not on your PATH. Keep the output attached to the same file hash or release identifier so results from two builds are not mixed. Command reference.

Interpret each field correctly

applicationId is the installation and Google Play identity. versionCode is the increasing integer used to distinguish releases. versionName is the human-readable label; it is not required to follow semantic versioning, and its lexical order does not control Android updates.

minSdk describes the minimum platform level declared by the build. targetSdk opts the app into platform behavior associated with that target. Neither field is a direct measurement of quality or a complete device-support promise. Native ABI requirements, declared hardware features and distribution settings can still exclude devices.

Do not infer compileSdk from targetSdk

A common metadata error is reporting the target SDK as the compile SDK. They are different build settings. If the inspection method does not reliably expose compile-time metadata, record compileSdk as unavailable and obtain it from the build configuration instead.

Similarly, a label resource may be localized. The visible app name in one resource configuration should not be treated as the only possible name users see. Android versioning.

Build a release-friendly record

A practical record looks like this:

The values above are illustrative, not results from an analyzed customer APK.

Resolve mismatches before uploading

If an app's displayed name is correct but its application ID is wrong, rebuilding or uploading more screenshots will not fix the identity mismatch. Check product flavors and applicationIdSuffix. If the version code is reused, create a legitimate new release build rather than renaming the existing file.

APKLint's inspector is useful for a readable overview. When you need authoritative build settings, consult the release configuration; when you need integrity assurance, run a separate signature verification. An “APK info” utility is not necessarily an antivirus or a store-eligibility checker.