F-Droid App stuck at 3.29.1 what's the deal?

[Oclair]

⚠️ Before posting ⚠️

• [X] This is a bug, not a question or an enhancement.
• [X] I've searched for similar issues and didn't find a duplicate.
• [X] I've written a clear and descriptive title for this issue, not just "Bug" or "Crash".
• [X] I agree to follow Nextcloud's Code of Conduct.

Steps to reproduce

Nextcloud offers its android app on F-droid, yet no updates since 3.29.1... Please ensure clients are being synced on alternative app stores!

Have a nice day, and thank you for your contributions to the community <3

Expected behaviour

latest updates are available in a reasonable timely manner.

Actual behaviour

No updates leaving users with outdated clients

Android version

Grapheneos 2024083100 pixel7a F-Droid 1.20.0

Device brand and model

google Pixel7a

Stock or custom OS?

Custom (explain in "additional information")

Nextcloud android app version

3.29.1

Nextcloud server version

any

Using a reverse proxy?

No

Android logs

No response

Server error logs

No response

Additional information

No response

[AndyScherzinger]

@tobiasKaminsky seems https://gitlab.com/fdroid/fdroiddata/-/merge_requests/15281/diffs is the last one pushed to f-droid

[RITFW]

I'm really grateful that you offer Nexcloud on F-Droid as an additional distribution channel and for all the effort you put into it.

In order to be able to decide if I should switch to another distribution channel, I would like to know if it is planned to keep the app on F-Droid in the future.

[AndyScherzinger]

In order to be able to decide if I should switch to another distribution channel, I would like to know if it is planned to keep the app on F-Droid in the future.

@RITFW I can assure you that we are fully committed to supporting f-droid as a distribution channel, for it being an alternative to restrictive channels like Google Play but also for its openness and OSS nature.

I am working on getting this resolved while it will also afterwards depend on f-droid themselves since apps are build and published exclusively by f-droid, not the original app authors.

[RITFW]

@AndyScherzinger

In order to be able to decide if I should switch to another distribution channel, I would like to know if it is planned to keep the app on F-Droid in the future.

@RITFW I can assure you that we are fully committed to supporting f-droid as a distribution channel, for it being an alternative to restrictive channels like Google Play but also for its openness and OSS nature.

I am working on getting this resolved while it will also afterwards depend on f-droid themselves since apps are build and published exclusively by f-droid, not the original app authors.

Thank you! I highly appreciate this.

[RITFW]

@AndyScherzinger , @tobiasKaminsky

Thanks a lot: F-Droid merge request

Highly appreciated.

[lesensei]

Well, the merge was accepted and the build was successful on september 6th, but afaict the f-droid store still serves version 3.29.1. I guess the problem is on their side, but I'm not versed enough in the ways of f-droid to understand what's happening, so I don't know if the MR there should/could be reopened ? Or maybe there's a normal delay between the build and the availability ?

[AndyScherzinger]

@lesensei it means all automatic steps have been taken, the publish is a manual one done by a f-droid staff member. So re-opening the PR won't help. best you can do is to ping the staff member - in this case licaon-kter

[Oclair]

Another project I follow also has issues in the last few months with F-Droid's lethargic response for updated software published on their app store...

[RITFW]

Apparently this time it's because a full disk on the update server. They are working on it.

Mastodon announcement (They only mention it in the second half of the post)

[RITFW]

The 3.29.3 update is now available from the F-Droid repository. The website has not been updated yet, but it should be there soon.