Skip to content

Commit

Permalink
🐛 Fix issue where setExact is invoked when canScheduleExactAlarms is …
Browse files Browse the repository at this point in the history
…false

Tbh this is silly mistake that I didn't remove the setExact code..
  • Loading branch information
iqfareez committed Mar 10, 2024
1 parent 585c21e commit d4f2c37
Show file tree
Hide file tree
Showing 2 changed files with 0 additions and 10 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -219,11 +219,6 @@ private fun scheduleNextUpdate(context: Context) {
// guarantee the timing to be run exact as the time we assigned to it
alarmManager.set(AlarmManager.RTC, midnight.timeInMillis, pendingIntent)
Log.d(LOG_TAG, "scheduleNextUpdate: Didn't have permission-Scheduled NOT exact alarm")
alarmManager.setExact(
AlarmManager.RTC,
midnight.timeInMillis,
pendingIntent
);
return;
}
}
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -83,11 +83,6 @@ private fun scheduleNextUpdate(context: Context) {
// guarantee the timing to be run exact as the time we assigned to it
alarmManager.set(AlarmManager.RTC, midnight.timeInMillis, pendingIntent)
Log.d(LOG_TAG, "scheduleNextUpdate: Didn't have permission-Scheduled NOT exact alarm")
alarmManager.setExact(
AlarmManager.RTC,
midnight.timeInMillis,
pendingIntent
);
return;
}
}
Expand Down

0 comments on commit d4f2c37

Please sign in to comment.