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.

Sign up for GitHub

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

Jump to bottom

AlarmManager can only be used for exact alarms. #976

Open
wansiklee opened this issue Jan 29, 2024 · 7 comments · May be fixed by #981
Open

AlarmManager can only be used for exact alarms. #976

wansiklee opened this issue Jan 29, 2024 · 7 comments · May be fixed by #981

Comments

@wansiklee
Copy link

I want to use inexact alarms in the Notifee library's timestamp trigger.

I would like to use set or setAndAllowWhileIdle options similar to the URL https://developer.android.com/develop/background-work/services/alarms/schedule#inexact. However, the current AlarmManager options in Notifee appear to strictly enforce the use of exact alarms.

Although there are AlarmType options such as set and setAndAllowWhileIdle, based on the code, it seems that these options are effective only when using exact alarms.

So, starting from Android 12, even if you set the alarm as inexact, it won't ring unless you allow 'Alarm & reminder'.
@MichaelRando
Copy link

same

@wansiklee wansiklee linked a pull request Feb 6, 2024 that will close this issue
Open
@github-actions GitHub Actions
Copy link

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

@wansiklee
Copy link
Author

Not stale.

@github-actions GitHub Actions
Copy link

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

@wansiklee
Copy link
Author

Not stale.

@github-actions GitHub Actions
Copy link

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

@wansiklee
Copy link
Author

Not stale

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(android): fix an issue when using inexact alarms wansiklee/notifee
2 participants
@MichaelRando @wansiklee