Fix SPM support: remove FlutterFramework dependency#576
Open
danyabdo94 wants to merge 1 commit into
Open
Conversation
Flutter's build system automatically injects the Flutter framework for plugins. Having FlutterFramework as an explicit SPM dependency causes build failures when integrating via Flutter's native SPM support. Also adds explicit UIKit import since SPM doesn't provide prefix headers, and simplifies the header layout to use publicHeadersPath.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
FlutterFrameworkdependency fromPackage.swift— Flutter's build system automatically injects the Flutter framework for plugins, so having it as an explicit SPM dependency causes build failures when integrating viaflutter build ios#import <UIKit/UIKit.h>toFluttertoastPlugin.msince SPM doesn't provide prefix headersinclude/fluttertoast/subdirectory to source root and usepublicHeadersPath: ""Context
When using Flutter's built-in SPM support (
flutter config --enable-swift-package-manager), the currentPackage.swiftfails becauseFlutterFrameworkis not available as a resolved SPM package — Flutter resolves it through its own build pipeline instead.Test plan
flutter build iossucceeds with SPM enabled and zero CocoaPods fallback warningsflutter build ios --releaseproduces a valid IPA🤖 Generated with Claude Code