Conversation

Notices

1. muesli (fribbledom@mastodon.social)'s status on Friday, 13-Jan-2023 09:28:15 UTC muesli

   What's going on with fdroid? Every time I see an update notification, it tells me it failed parsing the package. Super annoying.

   • creideiki@mastodon.social's status on Friday, 13-Jan-2023 09:34:08 UTC Creideiki

     in reply to

     • muesli

     @fribbledom For a long time, I've had that error *when tapping the update notification*. If I instead open the F-Droid app, switch to the "Updates" tab and click the "Update" button for the app that wants to update, it works.

   • muesli (fribbledom@mastodon.social)'s status on Friday, 13-Jan-2023 09:34:37 UTC muesli

     in reply to

     • Creideiki

     @Creideiki exactly the same here!

   • muesli (fribbledom@mastodon.social)'s status on Friday, 13-Jan-2023 09:36:04 UTC muesli

     in reply to

     • Matthias Bach

     @marix

     It's been like that for a while now, across multiple devices. Slowly losing hope this will ever get fixed.

   • Matthias Bach (marix@chaos.social)'s status on Friday, 13-Jan-2023 09:36:06 UTC Matthias Bach

     in reply to

     • muesli

     @fribbledom has it only started for you recently? I have been observing this issue since I installed fdroid on my phone which was years ago.

   • muesli (fribbledom@mastodon.social)'s status on Friday, 13-Jan-2023 09:40:11 UTC muesli

     in reply to

     • a Claes unto himself 🇸🇪🇭🇰💙💛

     @clacke

     80gb of free space in my case.

   • a Claes unto himself 🇸🇪🇭🇰💙💛 (clacke@libranet.de)'s status on Friday, 13-Jan-2023 09:40:14 UTC a Claes unto himself 🇸🇪🇭🇰💙💛

     in reply to

     • muesli
     @fribbledom For me when this has happened, it has been because my device is running out of space.
   • muesli (fribbledom@mastodon.social)'s status on Friday, 13-Jan-2023 09:40:35 UTC muesli

     in reply to

     • Surendrajat

     @surendrajat

     The standard, "official" client.

   • Surendrajat (surendrajat@fosstodon.org)'s status on Friday, 13-Jan-2023 09:40:36 UTC Surendrajat

     in reply to

     • muesli

     @fribbledom what client are you using? I encountered this in past with Droidfy but not anymore.

   • muesli (fribbledom@mastodon.social)'s status on Friday, 13-Jan-2023 09:55:06 UTC muesli

     in reply to

     • Surendrajat
     • Hans-Christoph Steiner

     @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.

   • Hans-Christoph Steiner (eighthave@social.librem.one)'s status on Friday, 13-Jan-2023 09:55:07 UTC Hans-Christoph Steiner

     in reply to

     • muesli
     • Surendrajat

     @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.

   • muesli (fribbledom@mastodon.social)'s status on Friday, 13-Jan-2023 09:59:12 UTC muesli

     in reply to

     • Surendrajat
     • Hans-Christoph Steiner

     @eighthave @surendrajat

     For what it's worth, there are several tickets already, the oldest still open one from >3 years ago:

     https://gitlab.com/fdroid/fdroidclient/-/issues/1843

   • muesli (fribbledom@mastodon.social)'s status on Friday, 13-Jan-2023 10:31:04 UTC muesli

     in reply to

     • Surendrajat
     • Hans-Christoph Steiner

     @eighthave @surendrajat

     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.

   • Hans-Christoph Steiner (eighthave@social.librem.one)'s status on Friday, 13-Jan-2023 10:31:05 UTC Hans-Christoph Steiner

     in reply to

     • muesli
     • Surendrajat

     @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.

   • sqrt(-1) (mdkcore@mastodon.social)'s status on Friday, 13-Jan-2023 11:24:08 UTC sqrt(-1)

     in reply to

     • muesli

     @fribbledom
     this happened with me a long, long time ago, with a specific app (I do not remember which one), but didn't appear anymore here

   • muesli (fribbledom@mastodon.social)'s status on Friday, 13-Jan-2023 11:49:05 UTC muesli

     in reply to

     • Surendrajat
     • Hans-Christoph Steiner

     @surendrajat @eighthave

     Will do as soon as I see another update notification!

   • Surendrajat (surendrajat@fosstodon.org)'s status on Friday, 13-Jan-2023 11:49:06 UTC Surendrajat

     in reply to

     • muesli
     • Hans-Christoph Steiner

     @fribbledom @eighthave hey can you run adb logcat in terminal when you click on update button? the logcat will show the crash or whatever hopefully.

   • muesli (fribbledom@mastodon.social)'s status on Friday, 13-Jan-2023 11:49:16 UTC muesli

     in reply to

     • Surendrajat

     @surendrajat

     Nope, plain install.

   • Surendrajat (surendrajat@fosstodon.org)'s status on Friday, 13-Jan-2023 11:49:20 UTC Surendrajat

     in reply to

     • muesli

     @fribbledom Also are you using any unofficial mirror for f-droid repo?

   • JONATH~1.BAT (treppenwitz@mastodon.social)'s status on Friday, 13-Jan-2023 17:25:37 UTC JONATH~1.BAT

     in reply to

     • muesli

     @fribbledom
     Oh yeah I get that too. But opening the app and updating from there does seem to actually work.