I see some earlier notifications in the log (through around 11:30 this morning, your time) that were using a lowercase ‘action’ – double checked, I don’t see this happening automatically anywhere, so that may have been an issue in config.
Here’s what I see in the logs:
11:48, phone-side TAKEN
This one woke the app.
2021-06-12 11:48:24.413 [Info] [main] [WebhookManager.swift:212] sendEphemeral(request:) > sending: WebhookRequest(type: “fire_event”, data: [“event_type”: “mobile_app_notification_action”, “event_data”: [“action”: “TAKEN”]], localMetadata: nil)
11:49, phone-side SKIP
2021-06-12 11:49:44.665 [Info] [main] [WebhookManager.swift:212] sendEphemeral(request:) > sending: WebhookRequest(type: “fire_event”, data: [“event_type”: “mobile_app_notification_action”, “event_data”: [“action”: “SKIP”]], localMetadata: nil)
11:51, phone-side LATER
2021-06-12 11:51:07.510 [Info] [main] [WebhookManager.swift:212] sendEphemeral(request:) > sending: WebhookRequest(type: “fire_event”, data: [“event_type”: “mobile_app_notification_action”, “event_data”: [“action”: “LATER”]], localMetadata: nil)
11:53, phone-side TAKEN
2021-06-12 11:53:19.231 [Info] [main] [WebhookManager.swift:212] sendEphemeral(request:) > sending: WebhookRequest(type: “fire_event”, data: [“event_type”: “mobile_app_notification_action”, “event_data”: [“action”: “TAKEN”]], localMetadata: nil)
12:00, watch-side TAKEN, LATER, SKIP, TAKEN
2021-06-12 12:00:07.982 [Info] [main] [WebhookManager.swift:212] sendEphemeral(request:) > sending: WebhookRequest(type: “fire_event”, data: [“event_data”: [“action”: “TAKEN”], “event_type”: “mobile_app_notification_action”], localMetadata: nil)
2021-06-12 12:00:08.041 [Info] [main] [WebhookManager.swift:212] sendEphemeral(request:) > sending: WebhookRequest(type: “fire_event”, data: [“event_type”: “mobile_app_notification_action”, >“event_data”: [“action”: “LATER”]], localMetadata: nil)
2021-06-12 12:00:08.041 [Info] [main] [WebhookManager.swift:212] sendEphemeral(request:) > sending: WebhookRequest(type: “fire_event”, data: [“event_type”: “mobile_app_notification_action”, “event_data”: [“action”: “SKIP”]], localMetadata: nil)
2021-06-12 12:00:08.041 [Info] [main] [WebhookManager.swift:212] sendEphemeral(request:) > sending: WebhookRequest(type: “fire_event”, data: [“event_type”: “mobile_app_notification_action”, “event_data”: [“action”: “TAKEN”]], localMetadata: nil)
Clearly something caused the Watch<->App communication to all get batched up when the app was woken up around 12:00, but I’m not sure what the cause of that is. The Watch decides to try to send to the phone if it believes it’s going to be able to communicate ASAP, so it’s possible it was guessing wrong there.
It might be worth doing something like (noting the time for each):
- Go to Developer Tools, events, and listen for
mobile_app_notification_action - Send yourself a notification
- Respond to the notification
- Perform the action
- Look for the event firing in Developer Tools
It’s possible a restart of both devices will make the ‘immediate’ messaging get back to normal as this behavior is definitely abnormal. It does appear the events are firing, just delayed, so it doesn’t seem like something is getting lost, at least.