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

[Request]: Huawei and Honor phones system UI support

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
android, dart, flutter
Domain
mobile

Research direction

Start with share_plus's Android handling of SharePlus.instance.share and ShareParams.title, comparing the default path with the documented empty-title workaround on Honor and Huawei devices. Verify the change on an Honor or Huawei phone and confirm the default opens the OEM system sheet without requiring title: ''.

Written by the indexing model from the issue text.

Description

enhancement triage
Plugin

share_plus

Use case
Honor / Huawei: share_plus shows a plain chooser instead of the system OEM share sheet

Device: Honor phone

On Honor (and Huawei) devices, share_plus currently shows a plain Android chooser UI that looks different from the system / OEM share sheet used by native apps.

Current share_plus UI (default) | Expected OS / OEM share sheet

share_plus default UI on Honor | OS share sheet on Honor

Workaround that works today

Setting an empty title forces the system OEM sheet:

Dart
SharePlus.instance.share(
  ShareParams(
    // ...
    title: Platform.isAndroid ? '' : null, // required on Honor/Huawei to get the proper system sheet
  ),
);
Proposal

Request
Could share_plus default to the system / OEM share sheet on Honor and Huawei devices (instead of the plain chooser), so we don’t need the title: '' hack?
Thanks!

Dominant language
Dart
Stars
1.9k
Forks
1.3k
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

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.