|
Föderation EN Mi 14.05.2025 22:45:55 @fdroidorg a warning when update transitions to another (inferior) architecture would be awesome. (Or ability to ignore/filter them out altogether.) |
|
Föderation EN Fr 16.05.2025 14:14:25 @cobratbq F-Droid Client will update to the biggest versionCode that's compatible with your device, yes. Sometimes the "best" arch might not build on time, during a cycle. But we don't expect any 'downgrade' in the app experience by this. |
|
Föderation EN Fr 16.05.2025 14:37:32 @fdroidorg well, there was a mismatch in versioncode but not version for an app, with 32-bit having received slightly higher versioncode. I don't know of security-related concerns but sometimes OS may warn when using 32-bit apps. Downgrading isn't possible unfortunately, so then you're stuck with warnings. |
|
Föderation EN Fr 16.05.2025 15:45:15 @fdroidorg or checkboxes to (de)select supported architectures. And yes, I know I'm asking for relatively very unimportant features that may be some work to implement for little benefit. I am fully aware. So I'm just dropping the note as an FYI. 😅 |
|
Föderation EN So 18.05.2025 19:46:02 @cobratbq Note that the higher version code comes with the new app version, it's not a mistake. All architectures have a higher code for a new version. |
|
Föderation EN So 18.05.2025 19:49:30 @fdroidorg the same release version gets the same code for any supported arch. When the same release has one versioncode for one arch and a different versioncode for another arch of the same release, F-Droid blindly prefers the highest versioncode which implicitly selects the unfavorable arch. |
|
Föderation EN So 18.05.2025 20:08:45 @cobratbq The way metadata is used in F-Droid forces a different version code for each arch. We push developers to always favor better arches with the higher version code, eg. If armv7 be 1, then arm64 be 2, etc. If they do not enforce this, please open an issue upstream. |
|
Föderation EN So 18.05.2025 20:11:35 @fdroidorg that's clear. I stand corrected. Thanks. |
