Auto-fix for android buildFeatures
rules may add code to the wrong android { ... }
block
#460
Labels
bug
Something isn't working
If the target module has a convention plugin, that convention plugin may have its own non-Google
android { ... }
configuration block.example:
In this case, the
android
block isn't a configuration forBaseExtension
/LibraryExtension
/etc. It's something else entirely.But the existing Android parser will see this block and assume that it's Google's. It will add any auto-fixes there.
There's no perfect solution to this. A couple options:
android
blocks which aren't top-level. If it's top-level and an actual Android module, it'll work.The text was updated successfully, but these errors were encountered: