Hello, I write or change some little macros for my new car android 10 unit.
Problem: Between two calls of a action I use
"Wait before next action" with 5 seconds
This worked in all nearly 100 macros I wrote in the last years for my many devices.
Now the macro stops completely at this point. Any more actions don't run.
I tested some time and I found a problem in the old forum with nearly the same problem
There 5 second and more did not work, but 4 seconds 490 ms and less worked.
I tested it now on my equipment
I tried this in my macro and I have the same result!
4.990 Seconds work and 5.000 seconds bring the macro to stop.
It does not matter if the [ ] use scheduler is activated or not.
In the systemprotocol I find: (see picture)
"Failed to resume macro after wait before next, if was -1"
Ok - I used some hours to find and locate this bug in my macros. I copied a lot from my old device and no one worked correctly :-(
And I can do a workaround with repeated calls of a shorter macro.
But I think that many people will struggle over this bug, and therefore it should be fixed soon
Problem: Between two calls of a action I use
"Wait before next action" with 5 seconds
This worked in all nearly 100 macros I wrote in the last years for my many devices.
Now the macro stops completely at this point. Any more actions don't run.
I tested some time and I found a problem in the old forum with nearly the same problem
There 5 second and more did not work, but 4 seconds 490 ms and less worked.
I tested it now on my equipment
I tried this in my macro and I have the same result!
4.990 Seconds work and 5.000 seconds bring the macro to stop.
It does not matter if the [ ] use scheduler is activated or not.
In the systemprotocol I find: (see picture)
"Failed to resume macro after wait before next, if was -1"
Ok - I used some hours to find and locate this bug in my macros. I copied a lot from my old device and no one worked correctly :-(
And I can do a workaround with repeated calls of a shorter macro.
But I think that many people will struggle over this bug, and therefore it should be fixed soon