ignoramous
commented
2 weeks ago This is something we'd invest in if we had more time (or money to buy someone else's time) or had more users (rethink has a very very tiny userbase).
That said, you make valid points. We have done quite a bit on this front #336 / #1455 and after much effort, the easiest thing for us now is to integrate Firebase Crashlytics (it will be on Play Store builds only) and not spend anymore time on any custom solutions (which themselves end up having bugs) than we already have (multiple months at this point!)
We do want to build the kind of "report" you're requesting... to make our own lives easier in terms of bugs. Let's see if we ever find time.
There have been a few times where a solution (or at least a workaround) was just to disable a certain option.
As there are quite a few pages of options and it's unclear which are changed from the defaults, it's difficult to summarise my own configuration, and the settings I think are relevant and do mention tend to turn out not to be. (Though on most occasions you have successfully deduced from a log which setting I need to change 🙂)
It would perhaps be useful to have a button somewhere that copies a list of relevant settings for debugging in plain text, suitable for pasting into GitHub issues and the like. Perhaps the settings backup is suitable for this already, but that also includes potentially-sensitive options and logs that would need reviewing before posting.
Relatedly, a way to grab a copy of recent, anonymised (e.g. using hashes of domains / IP addresses) logs from within the app would also be handy, as extracting them with
logcator other tools can be a bit of a pain.