This post is famous: https://youtu.be/lAbgeJau3eE?t=270
Too bad that he stopped at post #2 and ignored the rest of the discussion, why let so much info ruin a good out of context?
I think it is safe to ignore that Side of Burrittos guy: a) he doesn’t care about free software and b) he gets many facts about F-Droid just blatently wrong, so he’s not doing basic research.
1 Like
another question:
Is it possible to find older versions of F-Droid apk on Gitlab or Github?
would like to find this one
Is it possible to find older versions of F-Droid apk on Gitlab or Github?
would like to find this one
there are links given at Running on old Androids · Wiki · F-Droid / wiki · GitLab
while this is not directly at github or gitlab, generally old versions can be found at F-Droid - F-Droid Archive Repository
1 Like
I really think this should be reconsidered.
It causes a HUGE inconvenience (and confusion) for users who want to install FDroid in multiple profiles because you cannot install lower versions of apps you already have installed (downgrade protection) and this is true even across profiles in modern Android. So it isn’t possible to install and then update if you already have a later version on another profile. Since there is no transparency on the website regarding the app version, it could be very easily be seen as some other issue to those who are unaware.
Examples of issues - Cannot install F-Droid - Invalid package - using profiles - #26 by Sohika9539
I think this far outweighs the potential downside of issues that may or may not occur. Even if they did, you could argue that this would improve stability as these niche bugs could be reported then fixed. If it really wasn’t reliable, I would say it shouldn’t have been in stable.
Yes, it is possible to download an .apk of the newest version, but you could say that about downloading an older version too. Has it been considered to host both that version and the latest on the website?
2 Likes
How did you create the profile?
If by using Insular or Shelter, they have a “clone app in profile” action that just copies the main profile APK that’s up to date
Never say never. Eventually things happen.
The irony is a little funny.
However, if you look closely, you will see that this bug affected new installs and upgrades from >= two versions ago. So, if this exact bug had been replicated in F-Droid, it still would have caused problems for hosting a really old version on the website and then instantly prompting to upgrade after installing the app. Hence, it still reinforces my position on this thread.
You’re grasping at straws c’mon 
1 Like
The core of the issue is that F-Droid is the only open-source project in the world that cannot agree internally if a release is beta or production.
App, “I have a new production release available.” Website, “No you don’t, that is still a beta release.” App, “Now I have another new production release available.” Website, “No, that is still a beta release.” App, “I don’t care what you say, I am going to prompt everyone who installs the old version from you to upgrade immediately. Because the new release is production.”
Until F-Droid sorts out this internal disagreement, it is a huge red flag waving to the world that says, “We are not ready for anyone to take us seriously.”
You can take any item from the “F-Droid is bad at X” (long) list and call that “OMG this is THE red flag”. Be it python or Debian or targetsdk or non-FOSS sdk/ndk or which APK is on website at one point.
I’m not sure I can force random FOSS projects to host whatever package I want, but you do you. 
1 Like
All I am asking is for F-Droid to agree internally if a release is beta or production. As I pointed out in my last post, this isn’t hard. Every other open-source project in the world can do it.
Can you think of even one other example, besides F-Droid, that has this problem?
eg. Imagine me saying that “It’s a red flag that you don’t you host the APK here: https://www.stoutner.com/privacy-browser-android/”
It’s not a problem for me…
I’m roaming the F-Droid · GitLab issues sections… I’m not sure I’d release anything as “slable” or “to be used”
So, what exactly are you recommending regarding the install version on the website and in the app?
I don’t think those can be compared. One site is not hosting an apk, but directing users to where they can get it (the latest version mind you) from multiple sources, while the other is hosting a download that doesn’t inform the user they are downloading an old version and requires them to upgrade afterwards, with no directions for the latest version apk on the website.
Of course it’s not the biggest issue in the world but the reasoning here is really dubious and I honestly think it’s just stubbornness and fear of the HYPOTHETICAL issue that could arise that would prevent people downloading the app suddenly. Not to mention it’d have to be something that doesn’t occur on upgrading but only on installing fresh or otherwise it’d be fixed. These things happen and people can understand if on a rare occasion there is some niche issue that they have to wait to be fixed. FDroid doesn’t seem to be pushing new features like the forks are that would make it unstable so I don’t see why this is a massive issue
1 Like
I understand your concerns as a dev (you are the dev, not me), at the same time normie users (and me) care more about fast index updates (to come in 1.16 ;)) and real auto-updates (maybe on Android 12 or later devices, maybe via Device Owner etc)
What version in on website is a moot point, imho, does that work? Fine, does that crash? Ok, open an issue… try the newer version from this apk, did it fix it? No? Bad… etc
Calling it “RED FLAG OMG” sounds like FUD to me…
An upgrade is not required in any shape or form… you can stay on the site version and NEVER* update it if you wish… just like your other apps… you install one version and later you are REQUIRED to update? You reject apps updates… right? For all apps…I’m sure.
*not quite as indexV2 is already live so you might want that in the future
Wouldn’t it be more appropriate to do the same with the latest version? Does it crash, OK open an issue… try the older version APK, did it fix it? No, bad
This way you’d be improving the stability of latest releases. And it’s what basically every other app does
1 Like
Right, think this was said before… feel free to test on multiple devices and Android versions, post those results here.