Procedure to pull bad release?

1

What is the procedure to pull a release on an emergency basis?

There is a release, Fossify Messenger, that is having bad effects on users’ phones. The author has pulled it from Google Play but claims there is no “halt button” for F-Droid. Surely this issue has arisen before.

2

I am not fully aware, but I know we can allow future installs for the same version to be stopped, and the same way as rollback is not allowed under Android, same logic goes for F-Droid.
@Licaon_Kter @linsui can comment and correct me.

But this warrants a question, which maybe is known. Is there a way to “halt” as stated in the git issue by Naveen?

3
2 Likes
4

There’s no instant way, see There's no dummy cycle | F-Droid - Free and Open Source Android App Repository

2 Likes
5

Thanks. I guess I am still a lot behind on my information.
Thanks for disabling it.

6

Thank-you for doing this so quickly.

I suggest f-droid come up with an official suggested course of action for developers when issues like this arrise. A set of “immediate actions” for if a bug causes an app to misbehave. You have lots of apps with developers of varying experience, and it would be good to be able to point a developer to an official list and say “consider this”

Suggested Immediate Actions For Developers When A Misbehaving Upgrade Affects Other Apps:

  1. Get the distribution of the bad version halted
  2. If the bad release introduced no database changes, and if the bad release made it into wide distribution, then make a new release of the last good version repackaged in a new versionn number. IE: revert in a way supported by android.
  3. Then fix the bugs and introduce the new feature at your leisure.

Which is basically, pull the alarm, attack the fire, then only when its out figure out the cause and address it.

You might consider a code of conduct that even insists on this as a condition of listing in case one developer’s app causes issues with a phone in general or other apps.