#10288 added a formal way to allow plugins to indicate which platforms they support, but any plugin that doesn't support iOS (as in, has no ios/ folder) will cause CocoaPods failures. This is because the Podspec uses .flutter-plugins, which isn't platform-specific and thus isn't subject to platform filtering.

When I added initial macOS plugin support I addressed this in a somewhat hacky way. While we could do the same on iOS, we should probably solve this by changing the use of .flutter-plugins instead (and update the macOS Podspec template to match). See also #39657