Bug? r293: copying a variable in an Expression sometimes failed

Support, Troubleshooting, & Help
1

Hi there,
I noticed the following issue in r293 (not before) when trying to copy an Expression with variables into another Expression: after pasting, the variable often is no longer a valid one:

Example:

image
image756Ă—433 25.3 KB

But this happen regardless if I restartet chrome or open a new tab or Expression - but not every time. I can not see any systematic when it happens.

Has someone see this too?

Regards Chris

2

Hi @ChrisF -

I just tried this myself on r293, and was able to successfully copy the variable, but you mentioned that it seems this issue comes and goes / is not consistent?

I will check with the team to see if anyone else internally has seen something like this!

3

I can only reproduce that behavior in the enabled state check from buttons (as known).
Is there a specific behavior that promotes this error? (Highlighting by double click, keyboard…)

4

@ChrisF the team has reported back that this is a known issue for expression editor in Automations & for enabled / disabled state in apps, but are you also seeing it in trigger editor?

5

Hi,
we are not using any automations and it happens non-reproducable in a button expression and reproducable in the button enabled state expression.

Because I know how difficult it is to reproduce such an issue, I normally try a lot before posting

Regards
Chris

6

Hi Chris,

Very much appreciate you taking the time test this yourself. I just want to confirm, when you say the issue is “non-reproducable in a button expression” - does that mean you do not see it on button expression, or does it mean that you do see the issue on button expression, but it is inconsistent and hard to reproduce?

We want to make sure our fix covers all areas where folks may be seeing the problem.

7

Hi Beth,

I do see this issue, as shown in the figure above, in the button trigger when using an expression and copying the whole text from one expression field into another fields. When this happen a reopening of the chrome tab may help but not every time.

I will ping back when I see this issue in other widget or if I found any circumstances this issue occurs.

Regards Chris

1 Like