The issue was a lack of backward compatibility with older AlarmSettings model when device rebooted. I added this code to ignore the reschedule with older models, in rescheduleAlarms:
if (alarm.notificationSettings == null) {
continue
}
I'm publishing this fix in release 4.0.3 in the next minutes.
The issue was a lack of backward compatibility with older AlarmSettings model when device rebooted. I added this code to ignore the reschedule with older models, in
rescheduleAlarms:I'm publishing this fix in release
4.0.3in the next minutes.