[Bug] Action blocks with notifications & dialogs

Eggerd

New member
Hey everyone,

first of all I would like to mention how useful I find this app - life changer.
Now to the bugs I believe to have found:


Action Blocks & Notifications

If you create a notification within an action block and configure the press/button action to invoke another action block, passed variables will not be inserted. So if I press the notification the invoked action block will get the literal string "[lv=someVar]" as input, instead of the variable value.

I assume this happens because the action block that creates the notification has already ended by the time the notification is pressed and thus its variables are no longer available. With a wait timer (e.g. 5 seconds) after the notification creation the scenario actually works. But of course, that's not really a solution to the problem (e.g. looping the action block until the notification is no longer present).

As a side note: It's a bit strange that notification press/button actions don't use the value that a variable had at the time the notification was created, but rather use the value it has at the time the action is triggered.


Action Blocks & Dialogs

Dialogs won't show if the action block that creates it is invoked by another action block - only the notification sound will play. The system log will state "Could not find macro in Confirm Next Actions". If the action block is invoked via "Test actions" it works.

Found a workaround by accident: Placing a HTTP request (e.g. to localhost) before the dialog and saving the HTTP response into a string variable somehow solves the problem - no clue why; didn't find any other working solution.



I attached two action blocks that can be used to test both cases by running "Test 1". To test the dialog issue, disable the HTTP request in "Test 2".
Please let me know if I'm doing something wrong or if anyone knows a workaround for the first issue (using macros won't work, because of the behavior mentioned in the side note).

Thanks :)


Regards,
Eggerd
 

Attachments

  • TestActionBlocks.zip
    2 KB · Views: 3

Eggerd

New member
Oh also, configuring the input/output params of a notifications press/button action only shows an empty drop-down for boolean inputs, if the notification is created within an action block - works correctly inside of macros.
 

Eggerd

New member
Sorry for the late response, the notification mail must have landed in the spam folder...

Sadly I believe there is still a problem. Now the input params configured in the "Display Notification" action get replaced with their value after the first execution. So an input param like "[lv=someVar]" gets replaced with (e.g.) "lorem ipsum" and stays that way. Therefore the action block will always receive the same input params, no matter what value "someVar" actually has.
 

MacroDroidDev

Administrator
Staff member
I definitely don't see this happening. If you are sure this is a real problem then please use report a bug in the troubleshooting section and include the macro that exhibits the problem and I will take a look.
 

Kr99

New member
I'm also seeing this kind of problem, but with passing arrays around.

I noticed though that sometimes it's the default values of the array that get stuck. I have to have default values to test with.

I also noticed some problems with installing a macro with action blocks, where the action blocks would be duplicated.

I also saw a third problem I haven't tracked down where sometimes an action clock will completely disappear. I was doing some complex stuff with notifications, dialogs and two related action blocks that called back into the each another from the button actions. But I don't know the root cause of the issue. It did seem like it happened while editing and testing them though.

In general the action blocks just don't feel reliable and ready for prime time.
 

Kr99

New member
Also I tried reporting these bus three times via the in app big report tool and it seems email isn't working. I didn't get any notification about an error. I tried fixing it but it didn't work. I think MD needs to request email permission, and it also needs to add a notification when emails don't work. (I also tried a macro that would email my wife).
 

elier.oez

New member
I'm also seeing this kind of problem, but with passing arrays around.

I noticed though that sometimes it's the default values of the array that get stuck. I have to have default values to test with.

I also noticed some problems with installing a macro with action blocks, where the action blocks would be duplicated.

I also saw a third problem I haven't tracked down where sometimes an action clock will completely disappear. I was doing some complex stuff with notifications, dialogs and two related action blocks that called back into the each another from the button actions. But I don't know the root cause of the issue. It did seem like it happened while editing and testing them though.

In general the action blocks just don't feel reliable and ready for prime time.
Hello everyone.
Does anyone have a solution for duplicating action blocks when calling them from notifications?
 
Top