Friday, 15 November 2019

Is there an example for using dynamic modules on the Play Store when the dynamic module is used by a library module and not from the main app?

I've looked over Google's examples and codelabs and they look pretty simple but they are for modules that the main app access directly. My problem is that I have a module that the main app never access directly.

Basically I have this:

App -> Module A -> Module B -> Module C

So App imports A as a gradle implementation, A imports B and B imports C.

I want C, that is rarely used and large, to be a dynamic module.

I've already set C to be apply plugin: 'com.android.dynamic-feature' but I'm getting stuck on the dependencies.

If I set dynamicFeatures = [':C'] inside the gradle file of B, it fails because Could not set unknown property 'dynamicFeatures' for object

If I set the dynamycFeatures plus the implement line on App I get Unable to resolve dependency for ':app@prodDebug/compileClasspath': Could not resolve project :C

So how do I do this with this project hierarchy?

Thanks.



from Is there an example for using dynamic modules on the Play Store when the dynamic module is used by a library module and not from the main app?

No comments:

Post a Comment