I have implemented actionable push notifications with a picture whenever my front door camera detects movement. I had implemented actions for those notifications using the old format (in configuration.yaml). Since switching to the new actions format, the notifications are very slow to display on my Apple watch. The notifications show up instantly but the picture doesn’t load instantly. Instead, I can only see a spinning wheel for a couple of seconds. That has never been the case before. Does anybody know what the reason for this could be? Thanks!
Notifications with both attachments and actions (specified in the notification) require the watch download the image, to work around an Apple bug where the pre-downloaded version is inaccessible on the watch.
1 Like
Thanks for the reply. But why was this never a problem before? I also used notifications with an attachment and actions and they showed up instantly on the watch… Is there any workaround or can we just hope for a fix from Apple?
It’s an unfortunate side-effect of the new actions; they require the app launches to handle the notification, and the system bug prevents the app from having access to the attached (by the phone) images. If the actions weren’t there it would work, because the system can access them. Apple mostly has ignored my bug report and not investigated.
It’s possible I can work around it by manually sending the attachment to the Watch if I know it’s likely going to be used, but the biggest issue is that developing for the Watch is an absolutely miserable experience because Apple’s tooling around it is terrible.
1 Like