Adding dependency on app with product flavors

Question

I'm trying out the Android's latest app packaging and delivery model, App Bundles.

I've created a dynamic feature module and defined a dependency on the main app.

implementation(':app')

Now my app module has different productFlavors.

productFlavors {
  free {
    ...
  }

  pro {
    ...
  }
}

My dynamic feature does not require any product flavors. But I now get the following error on gradle sync -

Unable to resolve dependency for ':dynamic_feature@debug/compileClasspath': 
Could not resolve project :app.

I can fix this by defining the same productFlavors in my dynamic feature module, but is it absolutely necessary?

I am generalizing a case where I have many different submodules and productFlavors and defining productFlavors in each module feels redundant.

Answer 1

In this case you'll have to declare a missingDimensionStrategy for the dynamic feature module which doesn't have the flavor.

In your com.android.dynamic-feature module you'd add something like this

android {
// other things
    defaultConfig {
        // other things
        missingDimensionStrategy 'pro' // or whichever dimension you want to use
    }
}

You can find more about this and why this is necessary in the documentation.