dynamic-feature

问题 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"

问题 Adding dynamic feature using a navigation graph like the one below and works fine with viewPager2, or another fragment, but not with a BottomNavigationView . Layout <?xml version="1.0" encoding="utf-8"?> <layout xmlns:android="http://schemas.android.com/apk/res/android" xmlns:app="http://schemas.android.com/apk/res-auto"> <androidx.constraintlayout.widget.ConstraintLayout android:layout_width="match_parent" android:layout_height="match_parent"> <FrameLayout android:id="@+id/nav_host_container

问题 Adding dynamic feature using a navigation graph like the one below and works fine with viewPager2, or another fragment, but not with a BottomNavigationView . Layout <?xml version="1.0" encoding="utf-8"?> <layout xmlns:android="http://schemas.android.com/apk/res/android" xmlns:app="http://schemas.android.com/apk/res-auto"> <androidx.constraintlayout.widget.ConstraintLayout android:layout_width="match_parent" android:layout_height="match_parent"> <FrameLayout android:id="@+id/nav_host_container

问题 I'm getting my feet wet with dynamic module split API delivery in order to break up my game app into Instant and Installable versions. I've been following the Codelabs tutorial here https://codelabs.developers.google.com/codelabs/on-demand-dynamic-delivery/index.html#0. Unfortunately it uses Kotlin for the MainActivity code, which is less specific than Java, but still fairly followable if you've done a Kotlin tutorial. The example includes accessing a text tile in an 'assets' folder in an

问题 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

问题 My project has dynamic feature module and I would like to generate debug or release APK including the dynamic feature. Currently I can get only base APK file. Basically I would generate an APK file like normal application. But I couldn't do with dynamic feature. Yes, I know dynamic feature will work based on AAB. Is there any ways to make a normal(base + all modules) APK file?. Please help on this. Thanks 回答1: You can specify if your on demand module needs to be included in the universal APK

问题 im trying to implement a dynamic feature where from my base module i should call some methods in the feature, buts its only possible to call base methods from the feature, is there any way to make feature code accessible from base module ? (i understand what can happen when feature is not installed) I've implemented it using the default google docs, so i have no different code or implementation Today without dynamic feature i have two .apks and im using communication thru AIDL, im trying to