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

[Request]: In share_plus, make it possible to pass `excludedActivityTypes` to iOS

Open
#3,075 0 comments 4 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
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
dart, flutter, ios
Domain
mobile

Research direction

Start by locating the share_plus Dart API and its iOS native implementation, then trace how sharing options reach UIActivityViewController. Done means an optional iosExcludedActivityTypes parameter is accepted, passed to iOS, and used to populate excludedActivityTypes without breaking existing calls.

Written by the indexing model from the issue text.

Description

enhancement triage
Plugin

share_plus

Use case

In Order to fullfill the MASVS-PLATFORM-1 requirement, one should, according to MASTG-TEST-0071 ensure that when sharing is used, only desired activity types are allowed.

For native iOS, this is done by adding the excluded ActivityTypes to UIActivityViewController.excludedActivityTypes before presenting the controller. However, the share_plus plugin currently does not allow to pass this information to the native implementation.

Proposal

I would propose to introduce a new optional named parameter iosExcludedActivityTypes that takes a nullable list of a dart-mapped ActivityTypes enum. This parameter can then be passed to the iOS implementation and be used there to populate the UIActivityViewController.excludedActivityTypes. It would be a simple, non breaking change.

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.