Our 3rd party Android library's manifest declares uses-permission entries for android.permission.BLUETOOTH and android.permission.BLUETOOTH_ADMIN, but our app does not use those bluetooth capabilities. As a result, our users see these app permissions during installation from GooglePlay, which creates confusion.
I have tried using the manifest merging approach by adding these lines to our app's manifest:
<uses-permission android:name="android.permission.BLUETOOTH" tools:node="remove" />
However, it does not change what appears in the permissions list during app installation from Google Play.
Do I have this right? Please tell me it's much simpler than this!