manifest-merging

How to use the new manifest merger (of Android Studio and Gradle)?

只谈情不闲聊 提交于 2019-11-29 21:31:38
Background In the past, when Eclipse&ADT were the official tools to develop for Android, you could simply use " manifestmerger.enabled=true " inside the " project.properties " of the app's project, and you got it merging all of the libraries' manifests automatically (and I've posted about it here ). This worked, sometimes. It had a lot of weird issues, and I always preferred to just avoid using it, and put what is needed into the main manifest file manually. The problem Somewhere on 2014, Google announced that the new Android-Studio (0.1 I think), together with Gradle, will allow you to choose

Possible to use multiple authorities with FileProvider?

瘦欲@ 提交于 2019-11-29 01:01:23
Background I maintain a library whose core functionality involves sharing programmatically-captured screenshots to external email applications. I use a FileProvider to accomplish this, which means my library's manifest contains a <provider> tag : <provider android:name="android.support.v4.content.FileProvider" android:authorities="${applicationId}.bugshaker.fileprovider" android:exported="false" android:grantUriPermissions="true"> <meta-data android:name="android.support.FILE_PROVIDER_PATHS" android:resource="@xml/filepaths" /> </provider> filepaths.xml is defined as follows: <paths> <files

How to use the new manifest merger (of Android Studio and Gradle)?

空扰寡人 提交于 2019-11-28 17:31:31
问题 Background In the past, when Eclipse&ADT were the official tools to develop for Android, you could simply use " manifestmerger.enabled=true " inside the " project.properties " of the app's project, and you got it merging all of the libraries' manifests automatically (and I've posted about it here). This worked, sometimes. It had a lot of weird issues, and I always preferred to just avoid using it, and put what is needed into the main manifest file manually. The problem Somewhere on 2014,

Possible to use multiple authorities with FileProvider?

最后都变了- 提交于 2019-11-27 14:33:32
问题 Background I maintain a library whose core functionality involves sharing programmatically-captured screenshots to external email applications. I use a FileProvider to accomplish this, which means my library's manifest contains a <provider> tag: <provider android:name="android.support.v4.content.FileProvider" android:authorities="${applicationId}.bugshaker.fileprovider" android:exported="false" android:grantUriPermissions="true"> <meta-data android:name="android.support.FILE_PROVIDER_PATHS"