Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SCHEDULE_EXACT_ALARM Permission need in Android 14 #795

Open
ThushalIntervest opened this issue Aug 14, 2023 · 5 comments
Open

SCHEDULE_EXACT_ALARM Permission need in Android 14 #795

ThushalIntervest opened this issue Aug 14, 2023 · 5 comments
Assignees
Labels
feature request New feature or request

Comments

@ThushalIntervest
Copy link

ThushalIntervest commented Aug 14, 2023

Why it is needed?

In my project, I am utilizing the SCHEDULE_EXACT_ALARM feature. With the transition to Android 14 and onwards, there is a change in permission handling. In previous Android versions, this permission was granted by default (ALLOWED). However, starting from Android 14, there is a shift, and the default behaviour for this permission has changed to being denied by default. Therefore, in order to continue using the SCHEDULE_EXACT_ALARM feature effectively in Android 14 and beyond, it is now necessary to explicitly request and obtain the appropriate permission from the user.

Possible implementation

No response

Code sample

No response

@truongduy997
Copy link

I also need this permission, please support me !!! 🥹 🥹 🥹
Screenshot 2023-09-07 at 23 17 47

@ThushalIntervest
Copy link
Author

You can use Notifee Libary to request for this permission.

await notifee.openAlarmPermissionSettings();

Otherwise, I didn't find any solution for this issue

@polar-sh polar-sh bot added the Fund Can be funded on Polar.sh label Oct 16, 2023
@zoontek zoontek removed the Fund Can be funded on Polar.sh label Oct 16, 2023
@nateshmbhat
Copy link

nateshmbhat commented Dec 13, 2023

AlarmNotificationSetting.ENABLED still comes true even if we haven't explicitly requested schedule_exact_alarm in android 14 (so the permission is not enabled but still gives enabled as true)

image

@ThushalIntervest
Copy link
Author

For me this works fine in android 14. This can be happen in Android 13.

@gustavomts
Copy link

Apparently, this is only a problem if your target SDK is >= 33

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants