You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Notification Interaction - Click action number 2 Cannot invoke action 2 notification has no actions java.lang.ArraylndexOutOfBoundsException
- Thread starter aitn
- Start date
All other notification and interaction macros work fine for other apps while being on DND. It's something specific with these apps.DND is used when notifications are not needed, so turning on DND and using notification triggers is inconsistent.
After all, it is not a standard text notification, and it may not work well.
@Dimlos Does the notification look standard or custom? I guess comparing with another one that always work I suppose it's custom.I already disabled battery optimization for it yesterday and it was working fine.
Here is the screenshot:
View attachment 5931
But note that this is when DND mode is turned off. I was able to get it to work even yesterday with the mode turned on without it showing.
Actually I'm seeing in the macro log, it did fail few times with the same error even yesterday, so not sure, maybe it worked once but failed the other times? Really weird.
Last edited:
The issue is happening even when not in DND mode for Session.I don't know what you want to use notification triggers for in DND, but it's not standard usage, so it may cause a glitch.
I have no idea how to solve it.
When the call is coming it seem to freeze macrodroid macro, the "Last activated" gets updated as soon as I hang up the call.It appears to be custom, but I can't be sure.
In any case, I have no idea how to resolve this.
@Dimlos @Endercraft Any idea why Macrodroid macro is frozen from execution until I hang up the Wire call?When the call is coming it seem to freeze macrodroid macro, the "Last activated" gets updated as soon as I hang up the call.
i.e. Macro is:
Trigger: When Notification Received Wire Content: Any, Ignore ongoing notifications: Checked, Prevent multiple triggers: Checked
Action: Popup message 123
To trigger it, I initiate a call to it without answering, but the 123 popup only shows AFTER the incoming call is finished meaning I hang up from the calling side. I don't think any incoming notification should cause Macrodroid macro to freeze like that, is it a bug?
@Dimlos Could you please try it and see if you can reproduce the issue with the same phone/app (as you already have both)?
How do I force/workaround the macro actions to fire despite the incoming notification/call that seem to cause them to freeze until that triggering event is done?
@MacroDroidDev My Do not disturb setting is turned ON - it works fine when it's turned OFF, but other notification received based macros work fine when it's turned ON without them getting frozen like it does with this particular app incoming notification which I think is exposing a bug with Macrodroid? But actually even when DND is turned off is still giving me issues not firing:
I have DND turned off, I can see the customized notification showing of the incoming call, but the popup message 123 is not firing until I hang up.
Here is the macro log:
18:05:07 Notification Received (Wire) test
18:05:07 Invoking Macro test test
18:05:07 Popup Message '123' test
The fact that Macrodroid is logging "Notification Received" means it was able to identify the notification coming from Wire, but it's being stuck at this point. Actually that one corresponds to another notification which is hang up unanswered.
Maybe the calling is not considered as incoming notification? I'll add content to it contains "calling".
Ok now it doesn't fire the "123" popup anymore, I guess there is no notification incoming for when calling. Ok so maybe it's working as expected... It's a problem with the Wire app...
Is there a way Macrodroid can identify the incoming widget/custom notification coming from Wire when calling to it?
Weird I'm testing @Dimlos macro and it's working fine, not sure why his works but mine doesn't sometimes it doesn't work... But it's not consistent either... Maybe because the Wire app notifications for incoming call is not consistently coming...?
Update: Ok I turned off battery optimization for it and turned on a setting in it's network settings called
"Keep Connection to Websocket ON
Improve receiving notifications by keeping a constant
connection to production. It will replace notification
services if Google Services are not available on your
device."
And it seem to work much better
And it seems like what makes the trigger really work is what @Dimlos did by unchecking these two (they're checked by default):
Ignore ongoing notifications
Prevent multiple triggers
Still randomly it would stop working sometimes, although I don't think it's Macrodroid fault as I don't see the "notication" as showing/coming, so probably some issues with the app. Not sure if it's because I'm being blocked for trying too many times lol... But when it does work, it's much better now (with some additional tweaking from my side), thank you.
Last edited:
@Dimlos @Endercraft Any idea why Macrodroid macro is frozen from execution until I hang up the Wire call?
i.e. Macro is:
Trigger: When Notification Received Wire Content: Any, Ignore ongoing notifications: Checked, Prevent multiple triggers: Checked
Action: Popup message 123
To trigger it, I initiate a call to it without answering, but the 123 popup only shows AFTER the incoming call is finished meaning I hang up from the calling side. I don't think any incoming notification should cause Macrodroid macro to freeze like that, is it a bug?
@Dimlos Could you please try it and see if you can reproduce the issue with the same phone/app (as you already have both)?
How do I force/workaround the macro actions to fire despite the incoming notification/call that seem to cause them to freeze until that triggering event is done?
@MacroDroidDev My Do not disturb setting is turned ON - it works fine when it's turned OFF, but other notification received based macros work fine when it's turned ON without them getting frozen like it does with this particular app incoming notification which I think is exposing a bug with Macrodroid? But actually even when DND is turned off is still giving me issues not firing:
I have DND turned off, I can see the customized notification showing of the incoming call, but the popup message 123 is not firing until I hang up.
Here is the macro log:
18:05:07 Notification Received (Wire) test
18:05:07 Invoking Macro test test
18:05:07 Popup Message '123' test
The fact that Macrodroid is logging "Notification Received" means it was able to identify the notification coming from Wire, but it's being stuck at this point. Actually that one corresponds to another notification which is hang up unanswered.
Maybe the calling is not considered as incoming notification? I'll add content to it contains "calling".
Ok now it doesn't fire the "123" popup anymore, I guess there is no notification incoming for when calling. Ok so maybe it's working as expected... It's a problem with the Wire app...
Is there a way Macrodroid can identify the incoming widget/custom notification coming from Wire when calling to it?
Weird I'm testing @Dimlos macro and it's working fine, not sure why his works but mine doesn't sometimes it doesn't work... But it's not consistent either... Maybe because the Wire app notifications for incoming call is not consistently coming...?
Update: Ok I turned off battery optimization for it and turned on a setting in it's network settings called
"Keep Connection to Websocket ON
Improve receiving notifications by keeping a constant
connection to production. It will replace notification
services if Google Services are not available on your
device."
And it seem to work much better
And it seems like what makes the trigger really work is what @Dimlos did by unchecking these two (they're checked by default):
Ignore ongoing notifications
Prevent multiple triggers
Still randomly it would stop working sometimes, although I don't think it's Macrodroid fault as I don't see the "notication" as showing/coming, so probably some issues with the app. Not sure if it's because I'm being blocked for trying too many times lol... But when it does work, it's much better now (with some additional tweaking from my side), thank you.
Hello @Dimlos @Endercraft @Jacob L et al,
I'm starting to experience this issue with another app that used to work with Notification Interaction (Click action number 2) but after the last app update it stopped working.
The behavior appears to be the same, the condition is met, but the execution is being frozen until the notification will disappear.
Could it be the notification thread is causing the Macrodroid action thread to get stuck somehow?
@MacroDroidDev Do you recall fixing an issue like that?
Basically the structure of the macro is like this:
Triggers:
Notification Received Any Content (from your app, you could use Wire as an example)
Actions:
If Notification Present (from your app) Contains some text "XXX"
----->Notification Interaction (Click action number 2)
But while the notification is being shown with the two buttons, nothing really happens.
The log shows the if condition is true, and supposedly it reaches the Notification Interaction, but it doesn't really click anything.
Even if I add a Popup Message "test" inside the if condition... It won't show it until the notification with the two buttons will disappear.
I also tried the UI Interaction X,Y to click on the second button, and still nothing happens.
The weird thing is that sometimes randomly it does work. But I can't get it to work consistently.
Any idea what's happening and how to solve this? Does it sound like a Macrodroid bug?
Update: Ok I think I was able to solve the problem by unchecking the "Ignore ongoing notifications" from the trigger. It works now.
Thanks.
Last edited: