Add Netmera iOS dependencies via SPM, remove CocoaPods integration#31
Merged
Conversation
netmera-emmar
approved these changes
Jul 22, 2026
Bump netmera_flutter_sdk to 3.2.0, which introduces Swift Package Manager support for the iOS plugin as an alternative to CocoaPods. Migrate the example app's iOS setup to use it instead of the previous CocoaPods-based integration. - Enable Flutter's project-level SPM support via `flutter.config.enable-swift-package-manager: true` in pubspec.yaml, so the setting applies for every contributor without needing a machine-wide `flutter config` toggle. - Add the Netmera swift-sdk package (https://github.com/Netmera/ swift-sdk, exact version 4.23.3) as a Swift Package dependency in Runner.xcodeproj, linking the NetmeraNotificationServiceExtension and NetmeraNotificationContentExtension products into the Runner target for Media Push support. - Remove the CocoaPods-based Netmera integration from the Podfile: drop the NetmeraNotificationServiceExtension / Content pods, the now-empty target blocks for the two notification extensions, and the Swinject BUILD_LIBRARY_FOR_DISTRIBUTION post_install workaround that CocoaPods needed but SPM does not. - Regenerate Podfile.lock; fluttertoast is now the only remaining CocoaPods dependency, since Firebase, app_links, and netmera_flutter_sdk are resolved via Flutter's generated Swift package instead. - Commit the resolved SwiftPM manifests (Package.resolved) for both the project and workspace so builds are reproducible across machines, mirroring what Podfile.lock does for CocoaPods. - Update the iOS setup section of README.md to document both integration paths (SPM recommended, CocoaPods still supported), matching the SDK's own updated documentation.
baki-netmera
force-pushed
the
task/spm-support
branch
from
July 22, 2026 11:57
e6b6e95 to
ee15889
Compare
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
2 participants
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.
Bump
netmera_flutter_sdkto3.2.0, which introduces Swift Package Manager support for the iOS plugin as an alternative to CocoaPods. Migrate the example app's iOS setup to use it instead of the previous CocoaPods-based integration.flutter.config.enable-swift-package-manager: truein pubspec.yaml, so the setting applies for every contributor without needing a machine-wideflutter configtoggle.Runner.xcodeproj, linking theNetmeraNotificationServiceExtensionandNetmeraNotificationContentExtensionproducts into theRunnertarget for Media Push support.Podfile: drop the NetmeraNotificationServiceExtension / Content pods, the now-empty target blocks for the two notification extensions, and theSwinjectBUILD_LIBRARY_FOR_DISTRIBUTIONpost_installworkaround that CocoaPods needed but SPM does not.README.mdto document both integration paths (SPM recommended, CocoaPods still supported), matching the SDK's own updated documentation.