我在 iOS 10.2 中遇到了一个带有 UNTimeIntervalNotificationTrigger
和 UNUserNotificationCenterDelegate
的奇怪错误。基本上,我创建的通知会立即被委托(delegate)接收,然后在正确的内部再次接收。只有在触发器上将重复属性设置为 true 时才会发生这种情况。
有没有其他人看到过这个问题?现在我想我需要检查委托(delegate)中的触发日期并与存储的注册日期进行比较 - 但我想尽可能避免这种情况。
创建通知的示例代码
let content = UNMutableNotificationContent()
content.body = "My notification message"
let trigger = UNTimeIntervalNotificationTrigger(timeInterval: 60, repeats: true)
let request = UNNotificationRequest(identifier: "MY_IDENTIFIER", content: content, trigger: trigger)
UNUserNotificationCenter.current().add(request, withCompletionHandler: nil)
UNUserNotificationCenterDelegate 在 .add 后直接触发
func userNotificationCenter(_ center: UNUserNotificationCenter, willPresent notification: UNNotification, withCompletionHandler completionHandler: @escaping (UNNotificationPresentationOptions) -> Void) {
// Code called here instantly when trigger repeats = true
// Code called again at proper interval as well (60 seconds)
}
如果我将触发器更改为重复错误,则不会发生
let trigger = UNTimeIntervalNotificationTrigger(timeInterval: 60, repeats: false)
最佳答案
我仍然没有找到根本问题,也没有看到/听到其他人遇到这个问题。与此同时,这是我的修复(虽然我希望它能够正常工作)。
我创建了一个字典来存储通知被触发的时间。我使用通知标识符作为键:
scheduledTimes[identifier] = CACurrentMediaTime()
UNUserNotificationCenter.current().add(request, withCompletionHandler: nil)
然后在委托(delegate)中,我可以将它与当前时间进行比较,看看我是否应该忽略它:
func userNotificationCenter(_ center: UNUserNotificationCenter, willPresent notification: UNNotification, withCompletionHandler completionHandler: @escaping (UNNotificationPresentationOptions) -> Void) {
let identifier = notification.request.identifier
// Required for 10.2?
// Adding a notification request to the notification center immediately fires this delegate when the trigger is set to repeat
if let scheduledTime = scheduledTimes[identifier] {
if CACurrentMediaTime() - scheduledTime < 1.0 {
completionHandler([])
return
}
}
// Parse the notification into an internal notification and show it
completionHandler([])
}
添加和委托(delegate)调用之间的时间很短,平均约为 0.04。
关于iOS 10.2 UNUserNotificationCenterDelegate/UNTimeIntervalNotificationTrigger 错误?,我们在Stack Overflow上找到一个类似的问题:https://stackoverflow.com/questions/41469726/