Version detection issue

[Ichthyosaurus69]

Different apps by the same author have detected errors,For example, for APP A-1.10.apk and APP B-2.20.apk, it will detect and prompt APP A-1.10 to update to APP B-2.20, because the version number of B is higher than that of A,But they are two different apps.

[rainxchzed]

Hey @Ichthyosaurus69 — great catch, this slipped through the previous fix which only caught F-Droid sibling variants.

Root cause: when the auto-picker falls through to "just pick the highest-version installable asset", it didn't check that the candidate filename actually belonged to the same app you originally installed. So APP A-1.10.apk (installed) and APP B-2.20.apk (some other app in the release) ended up swapped.

Fix landing in following update: PR #592 adds a "base-name stem" filter — the installer compares the filename prefix (everything that isn't a version number, arch, or flavor token) and refuses to swap apps with different stems. Falls back gracefully when a maintainer legitimately renames the binary.

Thanks for the report!