solkin
AntiFeatures
Would you consider providing a FOSS build flavor? Currently, your app is flagged with quite a few anti-features, which are a bit more than just "borderline" by the IzzyOnDroid App Inclusion Policy:
So to keep it listed, we'd need a build flavor that comes without the Play Installer Library (which makes no sense anyway, as your app is not listed at Google Play), and ideally also without AppMetrica. Removing the Play Installer Library will most likely also get rid of GMS; as it depends on that, it's probably what drags it in.
Checking with your build.gradle.kts, I cannot find GMS explicitly requested – but neither the referrer library; could it be that io.appmetrica.analytics:analytics is the only culprit there, and the others are just caused by that?
Hello! I'm already working on replacing AppMetrica with my own crash reporting system. AppMetrica is currently used to receive crash reports after AppCenter shutdown.
If it's just about crash reporting: maybe ACRA is woth a look? Chose the opt-in mail reporting there, and it would not even need the Tracking anti-feature.
@IzzySoft I have already created my own lightweight, convenient, open system for collecting crashes, events, and distributing builds: https://github.com/solkin/bananalytics
Oh! All fine then. Comes under a libre license as well I see (you might wish to upload the Apache license file so GH detects it properly).
Yay! And as expected, all 3 offenders gone 🥳 Plus APK size went down by almost 700 KB 🤗 Thanks a lot! Will have to add your library to our library definitions still then. Is the data transmission (crash reports etc) opt-in, or does it send data automatically by default without getting consent first? Because if it is opt-in, we can also drop the Tracking anti-feature.
Btw: I've adjusted the update check pattern here now (to v%v, meaning "look only for tags/releases starting with a v followed by versionName and ignore all others"), as otherwise your untagged-2850f3d35d384df38dc7 got in the way for some reason. I've checked back to v12.1 in 2023, this should match your tag naming pattern – so it's rather "just to let you know" (to keep it that way) 😉
PPS: and now that the "big offenders" are gone, I gave Reproducible Builds a try. Result:
--- END BUILD LOG ---
Keeping 'e8e5fbebf29fb64edce0ade0f0db06334dadccb3f7b035444b530bd9756b3b14-com.tomclaw.appsend-v18.2-upstream.apk'...
Keeping '5124ed9d6937b46d95bdc663e62050b22803b2d3312208b97b52bd26a18e7825-com.tomclaw.appsend-v18.2-unsigned.apk'...
Reproducible: True
So congrats: Appteka will now carry the green shield 🥳 Maybe you also want to head to our Badges & Shields page and take your pick? 😉
Hm, looks like your new library is pretty much obfuscated 🙈
The source code of the client library is also open, you can find it here: https://github.com/solkin/bananalytics-android
So congrats: Appteka will now carry the green shield 🥳 Maybe you also want to head to our Badges & Shields page and take your pick? 😉
Thank you! I will definitely choose the badge.
P.S.: Badge added
The source code of the client library is also open
I know, but in the app, it seems obfuscated in a way our library scanner cannot "detect" it. Wasn't meant as "accusation", just stating the fact why it won't show up in the library details 😉 It's a point we (at IzzyOnDroid) still need to work on…
P.S.: Badge added
Thanks! 🤗 If you want to, there's also the RB shield 😉 (just in case you missed that – it's of course not "mandatory" 🤪)