The standard, "official" client.
@fribbledom @surendrajat please file an issue so we can follow up on it: https://gitlab.com/fdroid/fdroidclient/-/issues
For most bugs, 90% of the work of fixing it must come from the affected person, since it is about describing how to reproduce the bug, and providing follow up info. I rarely see bugs or crashes like this on my own devices since the ones I encounter over the years, I have fixed. We want to fix all the bugs, but we need people to report them, and provide detailed info.
@fribbledom I can't remember it ever happing to me, or if it did it was transitory and easily fixed by updating again. I'm using an old and superslow Nokia 1.
For what it's worth, there are several tickets already, the oldest still open one from >3 years ago:
@fribbledom @surendrajat the key is providing enough information that a developer can reproduce the issue locally. Granted, that's often difficult. Without reproducing the issue locally, fixing bugs is basically just guesswork. That issue is a good example of not having enough information to reproduce, though people have posted some info.
Yeah sure, maintaining a couple dozen projects myself, I'm well aware of that. I'm still kinda baffled that not one of the F-Droid developers could reproduce this. I've just pinged about 10 fellow Android users & developers and every single one of them is running into this issue.
Happy to provide any info you need to debug this, but you'll have to let us know *how* we do that.
@fribbledom @surendrajat A lot of us are running Google-free these days, unfortunately that means we have slimmer coverage for Google devices, though I'm guessing a majority of our users run Google devices. That could be a factor here.
@eighthave @surendrajat
I agree and apologies for not checking the bug-tracker beforehand, but I've literally never met anyone not affected or annoyed by that bug. I assumed that's just how it is.