android_alarm_manager

• Both AndroidAlarmManager.oneShot and AndroidAlarmManager.periodic have an optional rescheduleOnReboot parameter which specifies whether the new alarm should be rescheduled to run after a reboot (default: false). If set to false, the alarm will not survive a device reboot.

• Requires AndroidManifest.xml to be updated to include the following entries:

  <!--Within the application tag body-->
  <uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED"/>
  
  <!--Within the manifest tag body-->
  <receiver
      android:name="io.flutter.plugins.androidalarmmanager.RebootBroadcastReceiver"
      android:enabled="false">
      <intent-filter>
          <action android:name="android.intent.action.BOOT_COMPLETED"></action>
      </intent-filter>
  </receiver>
  
  

Breaking change. Migrated the underlying AlarmService to utilize a BroadcastReceiver with a JobIntentService instead of a Service to handle processing of alarms. This requires AndroidManifest.xml to be updated to include the following entries:

      <service
          android:name="io.flutter.plugins.androidalarmmanager.AlarmService"
          android:permission="android.permission.BIND_JOB_SERVICE"
          android:exported="false"/>
      <receiver
          android:name="io.flutter.plugins.androidalarmmanager.AlarmBroadcastReceiver"
          android:exported="false"/>

Fixed issue where background service was not starting due to background execution restrictions on Android 8+ (see issue #26846).

Fixed issue where alarm events were ignored when the background isolate was still initializing. Alarm events are now queued if the background isolate has not completed initializing and are processed once initialization is complete.