I have received the following feedback from Apple:
This is correct behaviour.
If you have both a phone and watch app installed we’ll try to coordinate between phone and watch notifications if the phone is unlocked. If the app developer doesn’t send a notification on the phone the watch will timeout after 13 seconds and alert anyway.
The best solution to this would be to send the same notification on both devices ensuring the UNNotificationRequest.identifier matches on a per-instance basis.
This will let us alert and deduce correctly.
FelixII
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
I'm experiencing the same issue since watchOS 8.0. I've submitted a bug report: FB9842030
I've stumbled upon the same bug while working on my iOS 14 widgets. My current workaround is to convert the UIImage into Data and use the init(imageData: Data) initializer.
if let imageData = uiImage.pngData() {
		let inImage = INImage(imageData: imageData)
	...
}
I've noticed this issue as well. It only affects the watchOS 6 simulator though. I currently use Xcode 11.4 together with the watchOS 5.3 simulator to test UserInfo transfers.