proprietary dependency added with 2.8.0

[IzzySoft]

With the latest release, the Play Install Referrer Library was added – and dragged in Google Mobile Services and PlayStore libraries – all of them proprietary (non-libre) and thus heavily tainting your app. At IzzyOnDroid we'll now have to add 3 anti-features: NonFreeComp, NonFreeNet (was already there, looks like you've used some GMS stuff already) and Tracking (for the Install Referrer).

Is this really needed? People getting your app not from PlayStore decided so for a reason (not wanting Google's tracking). Maybe build flavors could help here, if you think it's needed for the PlayStore variant?

While I'm here: seeing the APK size, the app is already twice over the per-app size limit (30 MB at IzzyOnDroid) with a single APK (62 MB). Would you consider per-ABI splits for the APKs here? Each ABI contributes about 15 MB to the size. Dropping x86 thus would mean reducing the APK size by about 30 MB. Sticking with a single ABI of your choice (armeabi or arm64) at IzzyOnDroid might then even allow keeping 2 versions.

Thanks in advance!

[aburdiss]

Hey IzzySoft!

The addition must be added through a React Native core update, which I added with the 2.8.0 release. I don't usually handle any Android code myself, as I let React Native build that out for me. I can take a look when I get some time to see if there's anything I can do about the Google libraries or the size.

[IzzySoft]

Wow, at core – as if everything would be written for PlayStore only … 🤞 you find the culprit and can get rid of it. Maybe npm list or yarn why <moduleName> can help you narrow down what dragged in those libs. Until then: happy new year!