I am developing an Android project which includes two modules where one is a library module for producing .aar
files and another is a sample app utilising the produced .aar
file.
Thus, there are two AndroidManifest.xml
files in this project. Say I am developing a Bluetooth library, so I put permissions for bluetooth in library's manifest file. By including this library .aar
as dependency, can I omit the <uses-permission>
tag in the app's manifest file? In other words, does Android app "merge" (may be not literally but semantically) its dependent .aar
libraries' permissions?
My experience suggests that while some permissions tend to behave as above, others demand explicit declaration in application's AndroidManifest.xml
. I would like to know if my assumption is true, if there are any resources or documentations clearly distinguishing permissions those can reside in .aar
library's manifest and those required to be declared in application's own manifest file.
Thank you!
As far as I know libraries' manifests are merged into the main manifest. According to this document all permissions should be merged as well.