Bug #3016
parse minSdkVersion from APK to set <sdkver>
| Status: | Closed | Start date: | 03/01/2014 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | improved security/usability | |||
| Component: |
Description
one key value in the FDroid metadata is <sdkver> which is android:minSdkVersion in the AndroidManifest.xml. Unfortunately, ApplicationInfo only has targetSdkVersion. So we need to find a way to read this directly from the APK, I suppose.
Associated revisions
hard-code APK's minSdkVersion, targetSdkVersion is different
ApplicationInfo.targetSdkVersion provides the "minimum target version",
which is the version that the build was targeted to. This is different
than the minSdkVersion, which is the minimum version that the APK will run
on. It seems that the only way to get the minSdkVersion from the APK is to
parse it out of the AndroidManifest.xml... sigh...
refs #3016
parse minSdkVersion from AndroidManifest.xml
PackageManager doesn't give us minSdkVersion, so we have to parse it.
History
#1 Updated by hans almost 4 years ago
"The minimum SDK version this application targets" is different from "the minimum SDK version this application can run on it"
#2 Updated by hans over 3 years ago
- Status changed from New to Resolved
Applied in changeset kerplapp|commit:a9db3d34e561b1d09f52ca6d4222fcc49216a97c.
#3 Updated by hans over 3 years ago
- Status changed from Resolved to Closed