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

Android: the Notifications settings card is not rendered at all, so there is no way to learn that push doesn't exist

Open Beginner friendly
  • Is something wrong?
#7,824 0 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
88/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
android, dart, flutter
Domain
mobile

Research direction

Start in mobile/lib/features/settings/settings_page/notifications_section.dart and compare the Android path with the existing iOS unavailable-row behavior. Check its sole use in mobile/lib/features/settings/settings_page.dart:219. Done means Android settings renders a non-interactive Notifications card explaining that push is unavailable, instead of rendering nothing.

Written by the indexing model from the issue text.

Description

Describe the bug

On Android, Settings shows no Notifications section — not the toggle, not the "Unavailable in this build" row, nothing. Android has no push transport yet (#6092, #7482 both open), which is fine and expected; the bug is that the app is silent about it. An Android user's only way to find out that a locked phone will never alert is to wait a day and notice.

The iOS branch of the same widget already has the right behaviour for this case — it renders a disabled row reading "Push notifications — Unavailable in this build" when the gateway define is empty. Android never reaches that code.

Cause

mobile/lib/features/settings/settings_page/notifications_section.dart:7-10:

Widget build(BuildContext context, WidgetRef ref) {
  if (defaultTargetPlatform != TargetPlatform.iOS) {
    return const SizedBox.shrink();
  }

_NotificationsSection is the only notifications UI in mobile settings (mobile/lib/features/settings/settings_page.dart:219 is its sole use site), so the early return removes the entire surface on Android rather than degrading it.

Steps to reproduce

  1. Build and run the Flutter app on Android.
  2. Join or create a community.
  3. Open Settings.
  4. There is no Notifications card between the sections above it and "Remove community".

Expected behavior

The card renders on every platform. On Android it shows a non-interactive row stating that push notifications are not yet supported on Android, ideally linking #6092 so a user can follow or thumbs-up the work rather than filing a duplicate.

Actual behavior

Nothing renders. The absence is indistinguishable from "notifications are on and working".

Suggested fix

Replace the platform early-return with a platform branch that reuses the existing unavailable-row pattern:

if (defaultTargetPlatform != TargetPlatform.iOS) {
  return AppListCard(
    label: 'Notifications',
    verticalPadding: Grid.twelve,
    children: [
      AppListRow(
        key: const ValueKey('push-notifications-unsupported-platform'),
        icon: LucideIcons.bell,
        title: 'Push notifications',
        subtitle: 'Not yet supported on Android',
      ),
    ],
  );
}

Happy to open a PR if the copy is agreed.

Version and platform

  • Buzz version: 0.5.23
  • OS: Android
  • Relay: hosted twelfth-ai.communities.buzz.xyz, relay software 0.2.1
  • Verified at block/buzz@312cf67

Related: #6092, #7482

Dominant language
Rust
Stars
33.7k
Forks
4.4k
Avg merge
2d 6h
Merged PRs (30d)
177

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 block/buzz

All issues in block/buzz

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.