John Malatras

I'm seeing this too

I (and the rest of the Edge team) would really love this!

Hi, I've been debugging the NotificationServiceExtension target without issue. That's how I pinpointed that `OneSignalExtension.didReceiveNotificationExtensionRequest` is the cause of the delay. The logging issue I mentioned is specifically around getting...

Are you displaying these as a communication notifications in the extension? To be clear they're delivered immediately for us too when it's a plain notification. The delays only occur for...

Weird. The only notable differences I see are that: 1. Our sender has an `image` that's a `INImage` initialized from a URL 2. We're donating the intent via an `INInteraction`...

@emawby If the call is outside of the intent donation completion block then the notification isn't rendered as a communication notification

Interesting, I actually don't see an async version of `func didReceive(_ request: UNNotificationRequest, withContentHandler contentHandler: @escaping (UNNotificationContent) -> Void)` available despite it being in that doc. If I kick off...

@emawby I have what I believe should be similar semaphore functionality in Swift but still no cigar; doesn't fix the delay: ``` let semaphore = DispatchSemaphore(value: 0) interaction.donate { [weak...

Sorry for the delayed follow up @emawby - we had a potential fix out yet and wanted to let it bake for a bit to ensure nothing was unexpectedly going...

Any update on this? I'm seeing the same and makes this lane pretty much unusable. `message` is also ignored by the newer workflow API so we can only send static...