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

[Bug]: android notification channel id not used in CapacitorNotifications.schedule

Open Beginner friendly
  • Is something wrong?
#175 0 comments 0 reactions 0 assignees View on GitHub

@coffeemakr is already working on this.

Since Sep 29, 2026.

  • #176 by @coffeemakr — open

Assessment

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

Research direction

Start in Notification.kt and trace the Android implementation of CapacitorNotifications.schedule, focusing on how the schedule option's channelId is handled. Reproduce with the linked runner and inspect adb shell dumpsys notification --noredact | grep channel=; done means scheduling with channelId: 'my_channel' reports and uses that channel instead of debug.

Written by the indexing model from the issue text.

Description

Current Behavior

Notification.kt doesn't read channelId and uses defaultNotificationChannelID

Create a notification channel my_channel in the app
In the runner: CapacitorNotifications.schedule([{ id: 1, title: 'Test', body: 'Test', channelId: 'my_channel' }]).
adb shell dumpsys notification --noredact | grep channel=
channel=debug

Expected Behavior

The channel id from schedule option is used

Reproduction

https://github.com/coffeemakr/cap-bg-repro

Screenshots / Media

No response

Environment Details
$ npx cap doctor
💊   Capacitor Doctor  💊 

Latest Dependencies:

  @capacitor/cli: 8.5.2
  @capacitor/core: 8.5.2
  @capacitor/android: 8.5.2
  @capacitor/ios: 8.5.2

Installed Dependencies:

  @capacitor/ios: not installed
  @capacitor/cli: 8.5.2
  @capacitor/core: 8.5.2
  @capacitor/android: 8.5.2

[success] Android looking great! 👌
Versions Affected

3.0.0

Platforms Affected
  • iOS
  • Android
  • Web
Notes / Comments

No response

Dominant language
C
Stars
57
Forks
37
Avg merge
3d 17h
Merged PRs (30d)
3

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 ionic-team/capacitor-background-runner

All issues in ionic-team/capacitor-background-runner

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.