-
Notifications
You must be signed in to change notification settings - Fork 137
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
getDependencies task prints enormous amount of AmbiguousVariantSelectionException #202
Comments
Will there be an update here? The logs eat up all the logging and if there's an issue, I have to disable the plugin so I can read the message.. |
I'll offer a workaround I just invent. Not a solution for every log, but at least reduction of them.
with
It will not require modules to have defined flavors the same your main application does and it will match them regardless of requested configuration. PS: pontential solution is to also define all flavors for all modules. EDIT: Seems this has an issues with aapt when modules defines some resources/attrs, so probably defining flavors in modules is a prefered way. In our case, we've just excluded that task from building and keeping it only for production builds. |
Unfortunately, @zayo 's workaround didn't help us. Fortunately, this task isn't always needed and can be excluded from the task that originally depends on it, for example: This doesn't fix the root issue, only mitigates some of the cases (where we don't really need this task). Hope that it will get fixed soon, our build logs are currently littered with unnecessary warnings. |
Look here: #137 - this problem was reported Apr 20, 2020 - 1.5 year ago |
Another workaround is to use different library like this one. It's not the perfect solution but migration isn't difficult and after migration logs are finally not cluttered. |
Describe the bug
Running
:app:getDependencies
task on our Android project (with 26 gradle modules) takes minutes and prints an enormous amount of AmbiguousVariantSelectionException for each of our library modules, resulting in 150+ MB of text logs.Using AGP 7.0.2
Expected behavior
Correctly handle local library modules
Example log
Desktop
The text was updated successfully, but these errors were encountered: