LIBRE_BUILD sdk still pulls in gms dependencies

I’ve been investigating the element-android containing proprietary gms libraries again through the use of the jitsi-meet sdk, even though it’s explicitly using an sdk built with LIBRE_BUILD=true.

I believe this is happening because jitsi-meet sdk is now unconditionally including a library that (optionally?) depends on gms libs and only conditionally excluding these transitive dependencies. Previously it only conditionally included the libs in the not-LIBRE variant. See here: https://github.com/jitsi/jitsi-meet/blob/7a64bf006ea027b77564d8847570e1ac46ff0ec0/android/sdk/build.gradle#L53

Unfortunately the exclusion rules don’t propagate to consumers of the sdk, which need to be aware of the latest jitsi exclusion rules and apply them to the jitsi dependency themselves. I’d hope there’s a way of excluding these transitive dependencies at the jitsi sdk level, so I’m not sure how exactly. Maybe a modified (excluding the proprietary dependencies from the pom file) version of the react-native-device-info dependency could be published to the maven repo if we are doing a libre build?

Fix at element-android side: https://github.com/vector-im/element-android/pull/3125

I’d appreciate your input, @saghul 😃.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[licaon-kter]

@bmarty affects Element as well 😦 https://gitlab.com/fdroid/fdroiddata/-/issues/2596