I know, this is O.K. and this is not what I am trying to address.
Steps to reproduce the issue:
Disable all repositories, except the “Firefox F-Droid (unofficial)” one. This measure is only to exclude any other repositories from interfering with this test (i.e. it also happens exactly the same way, when other repositories are enabled).
Refresh repositories manually by hitting the “” button: The F-Droid client app emits a notification “Saving application details”, which is expected (once a day).
Hit the “” button again: The F-Droid client app emits the notification “Saving application details” another time; well, maybe the daily repo update just ran, so this could be correct.
Hit the “” button a third time: The F-Droid client app emits another notification “Saving application details”; now, this cannot be caused by the daily repo update!
One can hit the “” button a fourth, fifth and so on time: The F-Droid client app always emits another notification “Saving application details”; this is the issue I am trying to address.
When carrying out the same test sequence with any other well working F-Droid repository (e.g. F-Droid, F-Droid Archive, Guardian Project Official Releases, Guardian Project Archive, but also third party repositories as microG F-Droid Repo, I2P F-Droid Repo or Öffi - Public Transport Buddy) this does not happen, i.e. the F-Droid client app does not always emit the “Saving application details” notification and does not take a long time to do so.
Note that the time the F-Droid client app takes to perform “Saving application details” has been drastically reduced in recent releases of it, especially when using the new (v1) index format. But unfortunately:
The Öffi repo does not offer an index file in the new format, so I am stuck at the old one.
On my “production” phone I am stuck at the F-Droid client release 0.102 (for technical / maintenance reasons), which takes ages to perform “Saving application details”.
Technically the issue is present with any release of the F-Droid client app, i.e. the Unofficial Firefox F-Droid repo is the only repository always triggering a “Saving application details”.
@rfc2822 Any way you can add Firefox Nightly to the repo? I’ve looked but it doesn’t look like Mozilla offers a “bouncer” URL like the ones you used for Release/Beta (I opened a bug so maybe they will add it) so you might have to implement it slightly differently.
Instead the only URL for Nightly is something like this https://archive.mozilla.org/pub/mobile/nightly/latest-mozilla-central-android-api-16/fennec-59.0a1.multi.android-arm.apk which has the version number in it. You can pull the version code from the JSON here.
Please just send a merge request If you add nightlies, I guess the repo archive policy and how long the APK is kept in the APK directory should be checked, too.
I don’t know anything about GitLab CI so the most I could do is add the current URL, have 0 ideas on how to implement the version tracking or the other stuff you mentioned.
Hi,
I just noticed that my f-droid client says about the unofficial Firefox repo:
"This paket source has never been used…W
And indeed, all pages under https://rfc2822.gitlab.io/fdroid-firefox/ lead to a 404 error,
however, I still have Firefox 58.0.2 in my list of available apps, so the change must have been a recent one.
If not, maybe chime in. That’s being led by the official Ff Android lead @ Mozilla, so maybe you won’t have to host this yourself anymore.
Until then, I do get updates, but the repo still seems to have some structural issues, e.g., I don’t see any versions under any of the Ff apps (indeed, when I try to do so, F-Droid crashes!) & also receive same error as @spaetz above.
Hi, now Firefox Beta has the same issue as Firefox previously. It shows as ‘update available’ every week, despite being the same version. Not sure how to solve that problem or I would propose a merge request.
You were right. It seems these were really different Betas, which was just not visible when one looked at the version numbers in fdroid. Case solved, thanks .
” button: The F-Droid client app emits a notification “Saving application details”, which is expected (once a day).
If you add nightlies, I guess the repo archive policy and how long the APK is kept in the APK directory should be checked, too.
.