plus_plugins icon indicating copy to clipboard operation
plus_plugins copied to clipboard

android_alarm_manager_plus 2.0.5 not working periodically with 1 day interval

Open SaikiranReddy412 opened this issue 2 years ago • 3 comments

we are getting issues with android_alarm_manager_plus 2.0.5 not working periodically with 1 day interval and not firing every 24 hr

SaikiranReddy412 avatar May 26 '22 04:05 SaikiranReddy412

Please use the Bug template to fill a bug report and include all the information in it

miquelbeltran avatar May 31 '22 13:05 miquelbeltran

Even with missing information I feel it is related to https://github.com/fluttercommunity/plus_plugins/pull/810

vbuberen avatar Jun 19 '22 20:06 vbuberen

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 15 days

github-actions[bot] avatar Sep 18 '22 00:09 github-actions[bot]

instead of depending on alarm manager, it would be probably better to use Work Manager as it's preffered way of scheduling tasks on Android right now

charafau avatar Oct 07 '22 16:10 charafau

I mean, no. AlarmManager has a place (wanting to run a task at a precise time, e.g. an actual alarm) and WorkManager is more to schedule work in the background without worrying too much on when it is going to be done.

Now, on Flutter and given how flaky the plugin is, I would simply avoid using either if possible.

miquelbeltran avatar Oct 07 '22 17:10 miquelbeltran

@charafau Just no! See the docs for when to use WorkManager and when to use AlarmManager. AlarmManager has its place and is the only option to fight Doze Mode without internet connection.

Regarding the flakiness, just be aware of #1149, then when taking care of it, the plugin is reliable! Just use the right alarm type for your use case.

guewin avatar Dec 09 '22 12:12 guewin

You're right, I misread the docs. I was pretty sure that the work manager had a special API for alarm manager like tasks. Thanks 👍

charafau avatar Dec 09 '22 17:12 charafau

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 15 days

github-actions[bot] avatar Mar 10 '23 00:03 github-actions[bot]