smichel17
commented
7 years ago I did some work on how we keep track of state, to pre-emptively fix bugs that keep popping up every time I make a change. The upload is built from 4ddeb1e.
For anyone who's technically curious, the changes are about making actions more idemptotent, which is a fancy word for a simple concept: actions that have the same outcome no matter how many times you do them. For example, stopping Red Moon is idempotent, but toggling is not; setting a certain filter is idempotent, but swapping through filters (from the notification) is not. I'm also trying to reduce duplicate code, to avoid situations where sometimes a bug happens and sometimes it doesn't. This should help make bugs more consistently reproducible.
With any code changes, new bugs are bound to appear. The more testing I can do, the fewer bugs will make it into the next release. However, testing takes time, which I'm often short on.
It would be a great help if a group of people were willing to test debug builds before they're released. The easiest/best way is to install the debug version of the app. It has more logging enabled, and will install alongside the fdroid/gplay version, so it's easy to switch back if it breaks.
If you're interested, just subscribe to notifications for this issue. Each time there's something new to test, I'll upload a debug build to this folder (note: it includes a permalink to the latest build I've posted. Other note: I've linked http because my cert is old, but if you'd rather https, it works). Then I'll comment on this thread so anyone subscribed will receive a notification (I'll include the commit I built from, if you'd rather build yourself).
If you find bugs or want to give feedback about a new feature, just open an issue like normal :)