I confirm that I can reproduce the bug on mobile! I’m looking into it and will come back with a fixed version.
The bug is fixed ![]()
I’m open to further tests, still at this URL :
Hello @pierre-gilles
It’s still not working for me (same behavior as described above). You wanted me
I’m stumped
It works fine for me.
Yes yes, it’s no more complicated than that, I do the same test here and it works!
I don’t really know what to tell you then…
Does anyone else have the issue?
Good catch, that must be a bug in the « Send a message » component! I’ll look into it and get back to you ![]()
It’s OK on mobile.
I’m available if you’d like us to have a call to test together
I just retried with a scene made up of different actions, and it works.
When you tried to reproduce my case, did you do the same? (i.e. 2 action blocks with the same actions)
Maybe it’s the same issue as the one noted when only moving a single action? (for which you indicate a potential bug on the « Send a message » component)
Edit 1: I’m testing across all actions. So far, the same behavior is observed on the « Send a camera image » action for the action’s message only (ok for the user and the camera).
Edit 2: « Continue only if » block fails for the ‹ value › data only (ok for variable and operator)
Edit 3: « Make an HTTP request » block fails for the ‹ body › field (ok for the other fields regardless of the chosen « method »)
Edit 4: « Control a device » block fails for the calculated data (ok for a « simple » control)
Edit 5: I’ve tested everything except the cases where the house is specified (« if house empty », « if house not empty », « User seen at home » and « User left the home »). I’ll check those later if necessary.
@PhilippeMA actually I understand, the two bugs you reported are the same bug! ![]()
You get the impression that it doesn’t swap the blocks because the display isn’t refreshed (I’m aware of this bug, I know how to fix it), but it did swap the two blocks!
I’ll get back to you as soon as the issue is fixed.
@PhilippeMA Thanks for all your tests that really helped me debug! It was a bug in the component we use to inject variables, the behavior when the text changed from outside the component simply wasn’t implemented ![]()
I’ve pushed the fix, it should be good here:
I just tested it, it’s fine for me ![]()
Thanks @pierre-gilles
This feature is available in Gladys Assistant 4.25 ![]()
I’m closing this thread, if you encounter a bug please create a separate thread! ![]()