#10288 added a formal way to allow plugins to indicate which platforms they support, but any plugin that doesn't support Android (as in, has no android/ folder) will cause Gradle failures. It looks from initial investigation like this is because flutter.gradle uses .flutter-plugins, which isn't platform-specific and thus isn't subject to platform filtering.

Presumably we should move away from having a single .flutter-plugins at all, and migrate all current clients to new platform-specific versions.

Currently the only way to make, say, a desktop-specific plugin that doesn't break Android is with a dummy directory.