[Feature Request] Do not try an manage/update apps not installed by Neo-Store

[shift18]

Guidelines

• I have searched the issue tracker for open and closed issues that are similar to the feature request I want to file, without success.
• I'm on the latest version.
• I'm not using a test build (alpha/beta/release-candidate).
• This issue contains only one feature request.

Problem Description and Proposed Solution

Howdy!

I'd like to request that an option is to be added which makes it so that Neo-store does not try and manage/update apps not Previously installed OR Updated by Neo-Store itself.

Alternatives Considered

I know I can set Neo-Store to "ignore all new versions" on an per app basis but this isn't a neat solution if many apps aren't installed by Neo-Store.

Relevant information

• Device: Pixel TOKAY
• Android Version: 16
• ROM: GOS
• App's Version: 1.1.4
• Unrestricted battery usage
• Default session installer

Thank you for considering my request

[licaon-kter]

what's the use case here? I mean, don't you want the latest version of your apps?

[shift18]

what's the use case here? I mean, don't you want the latest version of your apps?

I often install apps from places other than neostore and f-droid repo.
The f-droid repo, (with a few exceptions) uses there own signing keys which means the apps arent compatible with the ones on github etc.

The end result of neostore trying to update apps from other sources is a an annoying permission prompt and a waste of bandwidth from downloading updates which can't be installed.

[licaon-kter]

My experience is only with F-Droid client, not Neo, but I don't expect Neo to download any update if the key is not the same.

Can you provide a test case? Eg. You installed what from where and Neo tried to update it from which repo.

Notice that apps can be reproducible so even if you find the APK on Github, Izzy repo and f-droid.org...it's the same APK with the same signature.

[machiav3lli]

@licaon-kter

My experience is only with F-Droid client, not Neo, but I don't expect Neo to download any update if the key is not the same.

That's true per default, but there's an option in NS to disable this check + there's apps that use the same signature on different sources e.g. Proton apps on GPlay and F-Droid. Which you explained in:

Notice that apps can be reproducible so even if you find the APK on Github, Izzy repo and f-droid.org...it's the same APK with the same signature.

[machiav3lli]

Now more into the technical side of the issue. I'd also like Aurora Store to respect this, but the issue is more complex: With some newer APIs it should be possible to check the "updates owner" but this API had a turbulent history with almost yearly changes and year for year getting less reliable. I already have a check that uses this API for this written isNSPackageUpdateOwner, but I still didn't integrate it, as it would come with some questions and other changes that I didn't won't to do when revamping the backend for 1.2.0.

So I'd consider this for future minor-releases.