As far as I know, the push notification must be answered within a certain time. Otherwise, the flow is canceled. Unfortunately, I do not know the time, sorry.
"This issue has already been reported by other users and Development is working hard to fix this issue. I can’t give any guarantees on when this issue will be found and resolved, but please know that it has been forwarded to our development team and it will be investigated. "
I had exactly the same problem, and tested many different ways (spent 2 days). In the end, I found that it was just a matter of restarting the mobile app.
I just try it on my mobile app and my wife’s mobile app but the problem is still there…
It’s strange because this issue appears only when I use Push notification with answer (AND card), there’s no issue when it’s use on THEN Card with a simple push notification.
Thanks @GH14 for trying to help, hope I won’t spent more than 2 days on this !
Sorry to say, but I just tested and it works
Android 10 - Samsung S9
Where do you look for your results? Can you share the flow with us?
What mobile phones did you test with, which OS name (versions)?
This is the common status and issues about Athom’s servers. Your push confirmation results would not end up there.
When I use timeline notifications for example, it works fine
Thank you for the additional information.
We have identified the bug, and are able to reproduce it.
Please note that unfortunately, I have no timeline for the fix.
I’m sorry for the inconvenience.
I also have the same problem with push confirmation (not the normal push notifications!). I have a Samsung S20ultra with Android 13. If I test a push confirmation and I have the Homey app open it even crashes. Hopefully this is fixed soon.
Samsung Galaxy s10+, Android 12 here, Homey App 6.11.10, with the same issue, presented itself on Wednesday already (after app update that happened on Tuesday evening) and was sent to support. Push Notification works, Push Confirmation crashes the Android Homey App (if open and active) when sent and shows “Network request failed” in advance testing. Fun times when you have flows that depending on that confirmation xD
Yes exatly same for me, it was why I use Simple log error message to escape this, but after some tests I think Push confirmation crashes the App (or something else) even if it’s closed because I don’t receive any Push notification after this issue… Except if I reload the App. So I just “cut” every Push Confirmation in my AF for the moment. Hope this issue will be fixed as soon as possible !
I usually use the Timeline/Push notify but will try Simple log, I created force buttons to escape confirmations xD a bit more manual labor and less automation but will do for now. Would be nice if bugs like this could be presented someplace so people can find it easily and as soon as it is confirmed by support
Hey, just test this workaround solution and thank you it’s a good way ! I can manage the confirmation with more than 2 answers ! Just a question because I discover Telegram with this test, confirmation buttons can’t be in the Push notification ? We need to open Telegram to find confirmation buttons ?
YW.
This doesn’t use push confirmations at all.
But what is the difference?
A: Push confirmation pops up @ your phone: press yes / no
B: Telegram question pops up @ your phone: press yes / no / some other answer
I mean, you can configure Telegram to send preview?