-
Notifications
You must be signed in to change notification settings - Fork 630
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flavor collision #141
Comments
Have you tried adding |
The idea looked promising, I didn't know this existed. All the dimensions in the sublib contain only one flavor, so flavor matching should be ok. If I build an apk without this plugin, and with the same settings, it builds just fine. |
|
#84 |
I guess I figured it out: The problem is in Looking forward for feedback. |
Fixed in 1.3.3 |
I've found, that if the sublib is using flavors, than the plugin requires the mainlib to use the same flavors.
I'm using "Flavor1" in the sublib, so there will be a task called "buildFlavor1DebugAar".
I'm not using any flavors for the main lib, so the same task will be called just "buildDebugAar".
The plugin will look for the task with the same name for the mainlib, and will say it can't find "buildFlavor1DebugAar".
As soon as I add "Flavor1" to the main lib, everything is fine.
The text was updated successfully, but these errors were encountered: