I noticed when updating OsmAnd~ from F-Droid that Obtainium presents me with a dialog to pick an APK when there are multiple choices for the most recent (human readable?) version.
It shows my device's supported ABIs at the bottom there, but it does not show the ABI of each available APK from F-Droid.
I do see this info in their v2 repo index, so it does seem to be available.
JSON "path" is like packages[x].versions[x].manifest.nativecode[], which is an array with an entry for the ABI(s?) of each release APK.
So my request would be for Obtainium to show the ABI of each file in that options list.
F-Droid itself shows it like this on the web:
Although in the android F-Droid app it does not show it, and seems to filter the list of APKs to the ones that are ABI-compatible with my device without ever showing the ABI of each.
I noticed when updating OsmAnd~ from F-Droid that Obtainium presents me with a dialog to pick an APK when there are multiple choices for the most recent (human readable?) version.
It shows my device's supported ABIs at the bottom there, but it does not show the ABI of each available APK from F-Droid. I do see this info in their v2 repo index, so it does seem to be available.
JSON "path" is like
packages[x].versions[x].manifest.nativecode[]
, which is an array with an entry for the ABI(s?) of each release APK.For example:
It is not (for whatever reason) in the per-app active packages API.
So my request would be for Obtainium to show the ABI of each file in that options list.
F-Droid itself shows it like this on the web: Although in the android F-Droid app it does not show it, and seems to filter the list of APKs to the ones that are ABI-compatible with my device without ever showing the ABI of each.