I develop watchfaces for WearOS. I'm trying to modularize my code, by creating a base module that contains the common code for all my projects. Amoung other things, it should contain the code responsible for the in-app purchases. For this reason, I have to add <uses-permission android:name="com.android.vending.BILLING"/>
. However, some projects don't have an in-app purchase. Therefore, these projects would inherit the BILLING
permission, but actually woudn't need it.
So my questions are:
- Is there a way around it? Like a way to conditionally specify aspects of the Manifest?
- What are the consequences if I simply let this
BILLING
permission in, even if it's not required? - More generally, are there more "dangerous" permissions to let in when not required?