manifest-merging


Gradle-only solution to modify App name based on Build Variant

核能气质少年 提交于 2019-12-23 09:50:29
问题 I am trying to modify my gradle file to allow for different names for my app based on Flavor and Build Type . So far, I have been successful in being concise with Flavor based naming using Manifest Merging techniques via the Android Gradle Plugin Docs Current These are the names of the applications on my home screen for both my debug and release builds. Flavor Debug App Name Release App Name -------- -------------- ---------------- entity_1 App Name App Name entity_2 App Name App Name ... ...

Resource merging in Instant Apps features modules

て烟熏妆下的殇ゞ 提交于 2019-12-21 02:28:13
问题 In an Instant App feature module, I'm importing an aar (using "api" statement from a maven repository) which contains an activity declaration in its manifest and a "style" resource used in this declaration. The resulting manifest merging fails because the style resource is not found in the base feature project. It seems resources from imported aar in features modules are not included in the base feature module. Since the plugin is still in alpha mode I'm not sure if I'm doing something wrong,

Using ${applicationId} in library manifest

a 夏天 提交于 2019-12-20 11:33:11
问题 I'm working on an SDK that uses an internal ContentProvider, I would like to use this SDK in a few projects, and declare it in the library manifest, so I've tried this: <provider android:name=".core.MyContentProvider" android:authorities="${applicationId}" android:exported="false"/> What happens is the ${applicationId} is replaced with the packageName of the library and not the top apk related applicationId... Is there a way to make sure that the launching applicationId would be placed in the

Can we download a payment application that uses HCE in phones with lower than Android Kit-Kat 4.4.x?

懵懂的女人 提交于 2019-12-12 04:15:19
问题 I understand from the official android web site https://developer.android.com/about/versions/kitkat.html which says that " Android 4.4 introduces new platform support for secure NFC-based transactions through Host Card Emulation (HCE), for payments,... " that we can not use HCE in the devices lower than Android Kit-Kat 4.4.x. But I want to ask if we can download an Android application which uses/contains HCE and its related classes on the device which has a version that lower than Android Kit

MANIFEST MERGER: It is possible to see the resulting mixed Manifest?

我的未来我决定 提交于 2019-12-04 17:13:45
问题 I have a library module with a huge manifest. Also i have a application module with a huge manifest very similar to my library manifest but with package name changes. Now i want to see the resulting mixed manifest of Manifest Merger process. How can i see it? 回答1: You find the manifest in your build folder, e.g. /project/module/build/intermediates/manifests/full/debug/AndroidManifest.xml 回答2: In Android Studio 3.3 you can also see Meged Manifest by clicking on Merged Manifest tab. It's showed

MANIFEST MERGER: It is possible to see the resulting mixed Manifest?

泄露秘密 提交于 2019-12-03 10:10:49
I have a library module with a huge manifest. Also i have a application module with a huge manifest very similar to my library manifest but with package name changes. Now i want to see the resulting mixed manifest of Manifest Merger process. How can i see it? You find the manifest in your build folder, e.g. /project/module/build/intermediates/manifests/full/debug/AndroidManifest.xml In Android Studio 3.3 you can also see Meged Manifest by clicking on Merged Manifest tab. It's showed at the bottom of the editor pane when you open your standard project manifest. see documentation: Merge multiple

Using ${applicationId} in library manifest

生来就可爱ヽ(ⅴ<●) 提交于 2019-12-03 01:38:00
I'm working on an SDK that uses an internal ContentProvider, I would like to use this SDK in a few projects, and declare it in the library manifest, so I've tried this: <provider android:name=".core.MyContentProvider" android:authorities="${applicationId}" android:exported="false"/> What happens is the ${applicationId} is replaced with the packageName of the library and not the top apk related applicationId... Is there a way to make sure that the launching applicationId would be placed in the android:authorities value? Was running into the same problem with several different variants and

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,

工具导航Map