[Feature Request] Reproducible builds updates on success only
- Dominant language
- Kotlin
- Stars
- 7.4k
- Forks
- 214
- PR merge metrics
- No merged PRs in 30d
Description
### Before you submit
- [x] I have searched the issue tracker for [open](https://github.com/Droid-ify/client/issues) and [closed](https://github.com/Droid-ify/client/issues?q=is%3Aissue+is%3Aclosed) issues that are similar to the feature request I want to file, without success.
- [x] I'm not requesting app support for a specific repo — that's up to repo maintainers
- [x] I understand this might not get built (Droid-ify is maintained by a single person)
### What's the problem?
An issue came up recently (https://floss.social/@IzzyOnDroidOrg/116859043090506449) where an app's reproducability failed on a new build requiring reinstall if a user had updated it.
### What would help?
The feature requested is to add an option in the parameters (up to you for the default) to only update reproducible built apps if the new version is itself reproducible too.
### Alternatives?
Apparently Neostore has such a feature, but I prefer Droidify.
### Anything else?
_No response_
Contributor guide
Research direction
No files, tests, or entry points are named. Start by locating the parameters/settings implementation and the app-update flow, then trace how reproducibility is represented for available versions. Done means an option controls whether an update proceeds only when the new version is reproducible, with the default decided and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100