Macro hangs after 'Confirm Next' timeout

O

Olof

New member
I am trying to use the Confirm Next action as a message window that explains to the user what is going to happen next and why. The user won't have to click anything, just read the message and when he's done he may click OK or just wait until the window disappears automatically. Something like:

Title: Warning
Dialog message: This app is going to close because the battery is low
Positive button: OK
Negative button: no text > no button
Cancel after timeout: checked
Timeout: 30s

Everything deems to look and work fine. Problem is that after the timeout has made the message disappear, all macro actions after the Confirm Next action are blocked. Yes, I can uncheck the 'cancel after timeout' box. But when I do that, the timeout function will be disabled as well and the message will wait forever. Creating a Cancel button does not help either. Timeout will always block any subsequent action. Clicking OK in the Confirm Next window is working as it should.

What am I missing? I am sure there must be a solution but I simply don't see it. This way, the timeout function seems rather useless...

Olof

Samsung Galaxy A34, Android 14. Macrodroid 5.42.6 Pro, MD helper 1.14
 
D

Dm114

Well-known member
Olof said:
I am trying to use the Confirm Next action as a message window that explains to the user what is going to happen next and why. The user won't have to click anything, just read the message and when he's done he may click OK or just wait until the window disappears automatically. Something like:

Title: Warning
Dialog message: This app is going to close because the battery is low
Positive button: OK
Negative button: no text > no button
Cancel after timeout: checked
Timeout: 30s

Everything deems to look and work fine. Problem is that after the timeout has made the message disappear, all macro actions after the Confirm Next action are blocked. Yes, I can uncheck the 'cancel after timeout' box. But when I do that, the timeout function will be disabled as well and the message will wait forever. Creating a Cancel button does not help either. Timeout will always block any subsequent action. Clicking OK in the Confirm Next window is working as it should.

What am I missing? I am sure there must be a solution but I simply don't see it. This way, the timeout function seems rather useless...

Olof

Samsung Galaxy A34, Android 14. Macrodroid 5.42.6 Pro, MD helper 1.14
Click to expand...
For me it works nicely
 
MacroDroidDev

MacroDroidDev

Administrator
Staff member
Olof said:
I am trying to use the Confirm Next action as a message window that explains to the user what is going to happen next and why. The user won't have to click anything, just read the message and when he's done he may click OK or just wait until the window disappears automatically. Something like:

Title: Warning
Dialog message: This app is going to close because the battery is low
Positive button: OK
Negative button: no text > no button
Cancel after timeout: checked
Timeout: 30s

Everything deems to look and work fine. Problem is that after the timeout has made the message disappear, all macro actions after the Confirm Next action are blocked. Yes, I can uncheck the 'cancel after timeout' box. But when I do that, the timeout function will be disabled as well and the message will wait forever. Creating a Cancel button does not help either. Timeout will always block any subsequent action. Clicking OK in the Confirm Next window is working as it should.

What am I missing? I am sure there must be a solution but I simply don't see it. This way, the timeout function seems rather useless...

Olof

Samsung Galaxy A34, Android 14. Macrodroid 5.42.6 Pro, MD helper 1.14
Click to expand...
Please use report a bug in troubleshooting as this is not working how it should so I'd like to see the logs from your device to see if there are any clues in there.
 
O

Olof

New member
Sorry, I can't show you the log files. I cleared them a week ago as the files had become too big to work with. I found a work around using Popup Message.
Thank you and sorry again,
Olof
 
You must log in or register to reply here.
Top