Not showing and update notifications

• Device OS and version: LineageOS 13
• Device model/manufacturer: ks01lte Samsung
• F-Droid version (in the About screen): 0.103-alpha3

What did you do? (clear steps if possible)

I was made aware of available updates via an external app "ApkTrack" and started F-Droid to check for updates.

What did you expect to see?

A list of available updates within F-Droid.

What did you see instead?

Nothing, F-Droid alpha didn't list any updates as available. Even entering app details for e.g. K9-Mail didn't show an update, although one WAS available. It was also listed when clicking the versions field but not offered. Since alpha1 if I remember correctly I didn't get any update notifications from within F-Droid :-/.

Do you see the repo sync notification when you pull down?

Thanks for the report. In addition to @licaon-kter's question, I'd also be keen to know:

• If you go to "Settings" -> "Manage Repositories" -> "F-Droid", what does it say under "Last Updated"?
• When you view K9-Mail:
  • Which version did you have installed?
  • Which version was the highest version visible in the app details screen (once you expand "Versions")?
  • Which version had a star next to the version name? If an app is not manually specified as the "Suggested version" in our metadata, then it is possible to have an app which will be available via F-Droid, but it will not be suggested for updates.

I am not able to reproduce this, so we will need more info if we are to fix this.

added waiting-on-response label

@licaon-kter Yes, I see a repo sync notigication when pulling down. Also I see newer versions when clicking "Versions" in the app details.

@pserwylo

• I see a current time for "Last Updated" e.g. 08:08 this morning
• For K9-Mail, I was using version 5.206, while 5.207 was already available and listed under the "Versions" information as highest version
• I don't remember, which version had a star but currently a version from the F-Droid Archive repo has a start and that is version 2.203

Currently I see the problem again with OsmAnd~, I have 2.5.4 installed, 2.6.2 is available and 2.4.6 (again from F-Droid Archive repo) is the one with a star. I have enabled expert mode and unstable updates in settings if that helps.

Thanks, Dia

Same for me. This occurres on all updated progs like OsmAnd~, OpenAPK, NewPipe etc.

The priv. extension for fdroid is installed, if this helps.

I can add, that I do NOT have the priv. extension installed.

removed waiting-on-response label

Oh, that is very helpful, thanks for the detailed response @Diapolo.

@guest4711: Do you have the archive repo enabled also?

What is happening is that the repository with the lower position in the "Manage Repositories" screen takes priority. Because we default to having F-Droid Archive below F-Droid, then when both are enabled we prioritise apps from the archive repo. Clearly this is incorrect.

I'll have a look into this, thanks for the report.

indeed. I have a couple of repod enabled where the lowest are izzysoft, guardian-archive and fdroif-archive.

Is there an easy way to change thr order? Or do I have to delete the important ones to reenter?

Cheers guest4711.

The quick solution for this is to force "F-Droid" to always be below "F-Droid Archive", and hence always have a higher priority.

The better solution would be to have Archive repositories be aware that they are an archive for a particular other "main" repo. So the "F-Droid Archive" metadata would include a tag such as archive-for: https://f-droid.org/repo.

Given the difficulty and work involved in the second option, I think we should just force "F-Droid" (and indeed "Guardian Project") down one level in the Manage Repositories screen.

changed title from 0.103-alpha3 is not showing and update notifications to Not showing and update notifications

changed milestone to %0.103 - UX Overhaul

assigned to @pserwylo

mentioned in merge request !495 (closed)

We need to make this work right by default, changing the priorities should only be for customizing things.

@guest4711 follow !435 for the UI to change priorities

@pserwylo fdroidserver sets CurrentVersionCode (aka Suggested Version Code aka <marketvercode>) to the same thing for both the repo and the archive, so priority does matter. You can see that in the current index by looking for "com.fsck.k9" in these:

• https://f-droid.org/repo/index.xml
• https://f-droid.org/archive/index.xml

So the bug is somewhere else besides the changes in !495 (closed).

Oops priority does not matter.

I'm going to write a test for this which should fail now, then fix it so that we have test coverage for this problem.

mentioned in merge request !497 (merged)

closed via merge request !497 (merged)