We're experiencing that same problem.
After a lot of tries to reproduce this bug in debug mode with a lot of print statements,
my only conclusion is that system sometimes doesn't call `contentHandler` so notification is displayed not-modified.
Here's some code I used for debugging:
import UserNotifications
import UIKit
class NotificationService: UNNotificationServiceExtension {
var contentHandler: ((UNNotificationContent) -> Void)?
var bestAttemptContent: UNMutableNotificationContent?
override func didReceive(_ request: UNNotificationRequest,
withContentHandler contentHandler: @escaping (UNNotificationContent) -> Void) {
print("didReceive called")
self.contentHandler = contentHandler
bestAttemptContent = (request.content.mutableCopy() as? UNMutableNotificationContent)
if let bestAttemptContent = bestAttemptContent {
let notification = WANotification(userInfo: bestAttemptContent.userInfo)
print("notification created")
if let shortBody = notification.payload.bodyShort {
bestAttemptContent.body = shortBody /
print("body set")
} else {
print("no short body")
}
if let icon = notification.iconAttachment {
bestAttemptContent.attachments = [icon]
print("icon set")
} else {
print("no icon")
}
contentHandler(bestAttemptContent)
print("content handler called")
} else {
print("no best attempt content")
}
}
override func serviceExtensionTimeWillExpire() {
if let contentHandler = contentHandler, let bestAttemptContent = bestAttemptContent {
contentHandler(bestAttemptContent)
} else {
print("no content handler or best attempt content")
}
}
}
Now goes the interesting part: after reproducing this bug in debug mode, I sent 3 push notifications (with same payload), 2 were fine (had icon and modified body) but 1 still had unmodified content (no icon or body text changed), and what I got in console is this:
didReceive called
notification created
body set
icon set
content handler called
didReceive called
notification created
body set
icon set
content handler called
didReceive called
notification created
body set
icon set
content handler called
So, all of mine code was being called normally, except that one content handler wasn't been called internally by system.
I find this related to https://forums.developer.apple.com/message/197020#197020 because those steps (reinstall, reboot) helped me reproduce this bug while testing what's going on.
Any comment from Apple on this?
