Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Request]: Add formal support for Swift Package Manager (SPM)

Open
#3,827 1 comment 3 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
dart, flutter, swift

Research direction

Start with the referenced GeneratedPluginRegistrant.swift import failure, inspect the connectivity_plus Darwin source layout, and check whether a Package.swift exists. Test with Flutter's --enable-swift-package-manager configuration and confirm the plugin module is found without CocoaPods; done means the iOS/macOS sources are recognized as a standalone SPM module and the import succeeds.

Written by the indexing model from the issue text.

Description

enhancement triage
Plugin

connectivity_plus

Use case

I am migrating my Flutter project to use the new Swift Package Manager (SPM) feature (flutter config --enable-swift-package-manager). However, when SPM is enabled, the build fails because the native iOS module is not found.

The error occurs in GeneratedPluginRegistrant.swift:
Module 'connectivity_plus' not found

I have confirmed that disabling SPM and reverting to CocoaPods fixes the issue, but I would like to use SPM as it is becoming the standard for Flutter iOS development.

Proposal

Please update connectivity_plus to be fully compatible with Swift Package Manager. This involves:

Adding a valid Package.swift if missing.

Ensuring the Darwin (iOS/macOS) source files are structured to be recognized as a standalone module by Xcode when fetched via SPM.

Verifying that GeneratedPluginRegistrant can import the module correctly without CocoaPods header maps.

Dominant language
Dart
Stars
1.9k
Forks
1.3k
Avg merge
6d 16h
Merged PRs (30d)
16

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fluttercommunity/plus_plugins

All issues in fluttercommunity/plus_plugins

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.