dynamic-delivery

Android Provider in Dynamic Feature module not found in Base Module

泄露秘密 提交于 2021-01-27 03:43:41
问题 I am using some libraries in my dynamic feature module. These libraries are Adding some providers to the manifest. For example in my build.gradle file in the dynamic module: dependencies { ... implementation 'com.github.esafirm.android-image-picker:imagepicker:1.11.1' ... } This library adds the following tag to the manifest: <provider android:name="com.esafirm.imagepicker.helper.ImagePickerFileProvider" android:authorities="{$applicationId}.imagepicker.provider" android:exported="false"

How to fix “Program type already present” error when dynamic feature is using an external aar dependency

纵饮孤独 提交于 2020-01-06 06:46:22
问题 We have a 3rd party aar file that due to size considerations we decided to split to a separate dynamic-feature (module). Both main app and dynamic module are using com.google.code.gson:gson when they were in the same module we removed our dependency to gson , but now our main module needs it. The project build is fine, but when we try to build bundle(s) we get a "Program type already present: com.google.gson.FieldNamingPolicy$5" error We tried to exclude gson from the module's gradle: both in