Skip to main content

After importing this plugin to your project as usual, add the following to your AndroidManifest.xml within the <manifest></manifest> tags:

<uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED"/>
<uses-permission android:name="android.permission.WAKE_LOCK"/>
<!-- For apps with targetSDK=31 (Android 12) -->
<uses-permission android:name="android.permission.SCHEDULE_EXACT_ALARM"/>

Next, within the <application></application> tags, add:

<action android:name="android.intent.action.BOOT_COMPLETED" />

Check out our documentation website to learn more. Plus plugins documentation

Then in Dart code add:

import 'package:android_alarm_manager_plus/android_alarm_manager_plus.dart';
void printHello() {
final DateTime now =;
final int isolateId = Isolate.current.hashCode;
print("[$now] Hello, world! isolate=${isolateId} function='$printHello'");
main() async {
// Be sure to add this line if initialize() call happens before runApp()
await AndroidAlarmManager.initialize();
final int helloAlarmID = 0;
await AndroidAlarmManager.periodic(const Duration(minutes: 1), helloAlarmID, printHello);

If your app has targetSDK=31 (Android 12) and you would like to create alarms with alarmClock=true or exact=true be aware that user or system might cancel such alarms by revoking SCHEDULE_EXACT_ALARM permission. More info can be found in the official documentation

AndroidAlarmManagerPlus checks if the permission was revoked before scheduling exact alarms, so your app won't get SecurityException, but will report the issue in logs. However, in case when user grants SCHEDULE_EXACT_ALARM permission again AndroidAlarmManagerPlus won't reschedule canceled alarms automatically, so it is up to you to handle such cases.

printHello will then run (roughly) every minute, even if the main app ends. However, printHello will not run in the same isolate as the main application. Unlike threads, isolates do not share memory and communication between isolates must be done via message passing (see more documentation on isolates here).

Using other plugins in alarm callbacks#

If alarm callbacks will need access to other Flutter plugins, including the alarm manager plugin itself, it may be necessary to inform the background service how to initialize plugins depending on which Flutter Android embedding the application is using.

Plugin Development#

Running Flutter unit tests#

Run normally with flutter test from the root of the project.

Running Espresso tests#

The Espresso test runs the same sample code provided in example/lib/main.dart but is run using the Flutter Espresso plugin.

Modifying the main.dart will cause this test to fail.

This test will call into the example/lib/main_espresso.dart file which will enable Flutter Driver and then calls into the main.dart.

See for more info on why.

To run the test, run from the example/android folder:

./gradlew app:connectedAndroidTest -Ptarget=`pwd`/../lib/main_espresso.dart

Running End-to-end Flutter Driver tests#

To run the Flutter Driver tests, cd into example and run:

flutter driver test_driver/android_alarm_manager_e2e.dart