-
Notifications
You must be signed in to change notification settings - Fork 29.8k
Closed
Labels
p: toolingAffects the flutter_plugin_tools packageAffects the flutter_plugin_tools packageplatform-iosiOS applications specificallyiOS applications specifically
Description
Not sure I fully understand the current state of plugin tooling but somewhat related to #9580, wondering if it's possible to either
- Have
flutter createnot create a Podfile for iOS - Have mac._runPodInstall inspect the Podfile more closely to see if any dependencies actually exist rather than check the presence of the file
And only create the CocoaPods dependency when (I don't really know the state of these):
- Use inserts a dart+native plugin in pubspec
- Does something in Support consuming a plugin without having to write native code #7814 and make Podfile declarations while generating the native files
The messaging Warning: CocoaPods version 1.0.0 or greater not installed. Skipping pod install. is a bit ambiguous as it does not state what the consequences of continuing is. (#9035)
Metadata
Metadata
Assignees
Labels
p: toolingAffects the flutter_plugin_tools packageAffects the flutter_plugin_tools packageplatform-iosiOS applications specificallyiOS applications specifically