android.permission.SCHEDULE_EXACT_ALARM is unnecessarily in the manifest and causes issues

[xamplum]

Hello everyone,

The permission <uses-permission android:name="android.permission.SCHEDULE_EXACT_ALARM" />

in the Notifee AndroidManifest.xml causes several problems for us.

We only use Notifee to display push notifications. We do not use the AlarmManager.

Main problem: Since the manifests are "merged" in the build process, we ultimately also have the SCHEDULE_EXACT_ALARM permission in our final app manifest. Therefore:

1. our app is considered an "Alarms & reminders" app (see app info).
2. in the Android NotificationChannel sound settings, only alarm tones (i.e. continuous tones) are suggested and no short notification tones. This is a big issue for our user.

Example device: Pixel 6a both Android 13 and 14

The proposed solution:

Remove SCHEDULE_EXACT_ALARM from the Notifee AndroidManifest.

Deveolpers can add the Permission in their own apps if they need the functionality.

Thank you for your support!

[mikehardy]

Hi there! The ability to schedule exact alarms is important to Notifee, but there's no need for you to suffer for it if that specific thing isn't something you need.

Here is what turns up when you search about removing unwanted permissions, I've read it and it is easily adapted for whatever permission is unwanted, including this one: https://stackoverflow.com/a/45832083/9910298