-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proprietary components added #23
Comments
Thanks @IzzySoft for detailed analyzes. Indeed it seems these services were included by some react native third party package meant for QR code scanning. I will try to find alternative solutions to remove these dependencies. Till that time please use option 2 as you suggested. |
I'm no Android dev (and have no idea about RN development at all), so I cannot help with that much. Checking the definitions of my library scanner for a fitting match, I only found react-native-vision-camera explicitly naming RN and checked with their
Not sure what a good alternative would be. Fingers crossed you find one easily, which then is also easy to "swap in" 🤞 |
While waiting for a hopefully easy solution to that, may I ask for these two as well?
I'd say android {
dependenciesInfo {
// Disables dependency metadata when building APKs.
includeInApk = false
// Disables dependency metadata when building Android App Bundles.
includeInBundle = false
}
} For some background: that BLOB is supposed to be just a binary representation of your app's dependency tree. But as it's encrypted with a public key belonging to Google, only Google can read it – and nobody else can even verify what it really contains. |
Thanks @IzzySoft |
Thank you! Looking forward to that then 🤩 |
Hi @IzzySoft, |
Looks good, thanks! So I'll re-enable update checks now. |
Thanks @IzzySoft |
Today's updated added several proprietary components, essentially making the app no longer fully FOSS:
Hence I'll have now to either
The latter would be seen as a "red flag" for many folks looking for a good password manager – and in this case even violate inclusion criteria of the repo, as MLKit is also marked as Tracker – so I will for now take option 2, waiting for clarification. Options from your end would be:
Thanks in advance for consideration! I hope we can find a good solution here, so I can re-enable updates soon.
The text was updated successfully, but these errors were encountered: