I just imported LOOPER v2 https://library.tulip.co/apps/looper to my sandbox instance, and created simple test App which just iterate through “a”, “b”, and “c”.
I am expecting to see “0:a”, “1:b”, “2:c” when the loop runs.
I do see that when I start the loop by pressing the button.
However, I see “0:a”, “1:a”, “2:c” when I start the loop from step enter trigger (by setting the Begin loop flag to Yes).
Great timing for this question, we are in the process of releasing an updated looper widget with this fix! I will follow up here once we do. Should be coming shortly
@Beth@thorsten.langner
Please try this simple test App starting the looper v2.1 from the step enter trigger. app.json (13.9 KB)
I wanted to see “A”, “B”, “C” appear, but I see “{}” instead of “A”.
Thank you for pointing out the issue with the behavior of the Looper widget — you’re absolutely right, it was not functioning as expected. We’ve identified and fixed the problem, and the updated version will be available in the Tulip Library starting this Thursday, June 19.
In the meantime, we recommend checking out the following updated guide on unit testing the Looper widget, which may help you validate its behavior in your environment: Looper Unit Test
We really appreciate your feedback — insights like this help us improve the reliability and usefulness of widgets for the entire community.
However, I still see this “B”->“B”->“C” issue.
This happens when “Iteration” was not zero when “Begin Loop” became true.
It happens because the initializer “setValue(“Iteration”, 0);” is having the effect asynchronously.