- Sep 22, 2017
- 5
- 2
Is the iOS rich push notification "10-second GIF" actually showing the advertised 10 seconds for anyone?
To test this, I set up two Actions for the *same* camera.
The 1st action is to send a rich "Alert image".
The 2nd action is to send a rich "10-second GIF".
As an example, this camera triggered due to motion at hh:mm:ss = 10:00:00.
On the phone, I get a notification with an alert image showing the triggering frame;
the timestamp in the image is 10:00:00.
So far, so good.
I also get a notification with an animated image, but the "10-second GIF" doesn't actually show the triggering frame;
the timestamps in the animation start at 10:00:04 and go to 10:00:09.
So, it's more like a 5-second GIF that is delayed 4 seconds after the trigger.
I was expecting the animation to start at 10:00:00 and go to 10:00:10.
I'm wondering if this problem is unique to me or not.
Thanks!
To test this, I set up two Actions for the *same* camera.
The 1st action is to send a rich "Alert image".
The 2nd action is to send a rich "10-second GIF".
As an example, this camera triggered due to motion at hh:mm:ss = 10:00:00.
On the phone, I get a notification with an alert image showing the triggering frame;
the timestamp in the image is 10:00:00.
So far, so good.
I also get a notification with an animated image, but the "10-second GIF" doesn't actually show the triggering frame;
the timestamps in the animation start at 10:00:04 and go to 10:00:09.
So, it's more like a 5-second GIF that is delayed 4 seconds after the trigger.
I was expecting the animation to start at 10:00:00 and go to 10:00:10.
I'm wondering if this problem is unique to me or not.
Thanks!