Replies: 1 comment 2 replies
-
Our build scripts (should) make sure to NOT include Firebase for GitHub & F-Droid flavours, but only for Play Store (which also contains other Google-related APIs that Rethink uses; for example to prompt user for app updates): Lines 294 to 296 in 6fc4c28 We've found Firebase Crashlytics in our own testing to be super good at capturing logs relating to crashes. We intend to use it to stablize the app (as Rethink crashing in the background and thus "leaking" connections is also a major problem). We did take a stab at this with our built-in "bug reporter", and we spent considerable time on, but it has proven to be a too much of a hassle with its own bugs. Users who do report bugs on GitHub often don't follow-up with logs or bug reports making rectifying those issues (despite a LOT of back and forth) without any progress towards a fix. Rethink does not use Firebase "Analytics", just Crashlytics. More: #1455 Tools like Exodus (which is also used by other Android app scanners like Pithus) incorrectly label apps with "Analytics": Exodus-Privacy/exodus-core#97 On Play Store versions, users can disable Crashlytics auto-reporting crashes. With Loopback mode (Configure -> Network), users can redirect Rethink's own traffic within Rethink (except "connectivity checks" if enabled) to monitor it just like any other app. In the present versions, we don't let users create rules on Rethink, but that's a temporary measure, as blocking Rethink itself may cause confusion. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
All reactions