"Message matches" uses value of text field if there is a Self str variable

Huh, really weird
Never experienced this

5 Likes

This is very unusual, but most certainly a bug. However, I am not able to reproduce the bug because (for me) the reproduction steps were a bit complicated. I understand the bug, but not how to reproduce it, if that makes sense. And now that I think about it, it might not be a bug, but simply an error in the code. But, I can’t be exactly sure. Thanks for reporting this :).

2 Likes

is that not what a bug is?

5 Likes

no

bug:

🐛 

error:

albus_power.exe stopped working
1 Like

Bug

Woooooooooooooooooo

Error

Syntax error nooby coder

1 Like

but the syntax error is caused by a typo in the code, which is a bug

2 Likes

Well, yes. But I also like to think of bugs as a mistake the platform made. In this case, it could be made by the platform, or self-created.

1 Like

Ah thanks for the feedback about the reproduction steps — yeah I see it might be a bit convoluted. I wanted it to be detailed for the hopscotch team, but here is a quicker version:

Basically the code to test is this:

(In the third rule, ‘underneath’ the (Self) Name variable, put the text “oranges” in the “When message matches” bubble, before putting the variable in that bubble.)

In Play mode, when the object is tapped, it isn’t expected to change colour because (Self) Name has been set to “apples” at the start. But the object does change colour.

That is because it is reading the text underneath Self (Name), which is “oranges”. This is unexpected behaviour of the app (thus a bug) to me.

(The Self variable also doesn’t work as expected when the text underneath is empty i.e. it still doesn’t use the value of the Self variable)

4 Likes

Thank you for explaining that to me.

This is definitely a bug because I can reproduce it.

1 Like

Thank you for testing that out :smiley:

3 Likes

Your welcome. I am determined to help squash bugs.

1 Like

That was replying to

2 Likes

Oh wow that’s quite detailed and thorough debugging, thanks for linking that here. hopefully that helps THT to look into it.

I just saw your other bug report, I wonder if this part still happening? (when the self variable is not empty)

when I tested with the “when I get a message” block with non-empty Self variables, it seemed to work as expected

I am going to check later on again for that particular case, (I don’t have access to my iPad at the moment, and I’m not familiar enough with community-made tools yet)

I guess in the case of a message matching block being empty, I would expect the code in the When block to not be triggered ( it would ignore any messages)

4 Likes

It’s not. It was bugged even when it wasn’t empty before, but it is fixed now. It looks like they just forgot to put the same fix for message matches.

2 Likes

Clearly not Happening to me.

sQuAsH tHeM aNd MaKe ThEm InTo OrAnGe JuIcE

1 Like

Not orange juice, we’re making lemonade

2 Likes

Hey there! Thanks for reporting this! This issue should be fixed with v3.45.0!

7 Likes

Thank you so much for fixing it :smiley: I noticed it in the App Store update description ^^

I’ll close this topic.

4 Likes