BUG: Foreground service should not require POST_NOTIFICATIONS permission

[eoinoreilly30]

Expected behavior

The foreground service on Android should work without prompting the user for notifications permission. The Android docs state "Apps don't need to request the POST_NOTIFICATIONS permission in order to launch a foreground service"

Describe the bug (unexpected behavior)

When starting a call on Android the user is prompted to enable notifications permission. Notifications permission should not be required to start a foreground service.

Steps to reproduce

Join a call using pipecat react native. However, I have only reproduced this using react native Daily transport.

Screenshots

System information

• Device: Google Pixel 7
• OS, version: Android 16, sdk 36
• Browser, version:

Additional context

[bc-tinker]

We are also trying to remove this permission as android is discouraging it's use and preferring the use of the notifications permission

[filipi87]

Hi, thanks for reporting this.

On Android 13 (API 33+), POST_NOTIFICATIONS is generally required, but the mandatory foreground service notification is exempt from this permission.

Since this module only starts a foreground service and posts only the required ongoing notification, prompting the user for POST_NOTIFICATIONS is not necessary anymore in this case.

We’ll add this to our TODO list and update the permission handling.