This should fix issue #96 for the schedule of multiple alarms. The problem is that by using NSDate.date.timeIntervalSince1970, subsequent alarm schedules get the same ID and thus overwrite the previous schedule on iOS as per [UNNotificationRequest requestWithIdentifier: content: trigger:] documentation.
The proposed fix here will use the fire date to generate the alarm ID, it will work as long as no alarm date/times clashes.
This should fix issue #96 for the schedule of multiple alarms. The problem is that by using
NSDate.date.timeIntervalSince1970
, subsequent alarm schedules get the same ID and thus overwrite the previous schedule on iOS as per[UNNotificationRequest requestWithIdentifier: content: trigger:] documentation
.The proposed fix here will use the fire date to generate the alarm ID, it will work as long as no alarm date/times clashes.