Multiple Rule Corruptions

[chickwebb]

For the last day or two, editing Rules is all-too-frequently generating " An unexpected error has occurred trying to load the app" errors. The specific log message is "groovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (java.lang.Integer) values: [1]". It occurs when I'm editing conditional statements, typically when I try to erase or edit an existing one. For example, I create an IF/THEN condition, go back to edit it, hit "Erase", and get that error.

This happens to existing rules and brand new ones that haven't been installed yet. And, after I get the error, I cannot edit or create any conditional statements. Every attempt to do so generates the same error. Obviously, it's getting in the way, as I can't really touch anything right now for fear it'll blow up and I'll have to recreate it. Any thoughts on what might be going on here?

[anon47916022]

Are you using any of the browser navigation buttons when editing (e.g. back/forward buttons)? That's been known to corrupt rules.

When you say erase, do you mean you use the trash can icon to delete the action?

[bravenel]

@chickwebb

"groovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (java.lang.Integer) values: [1]".

Please show a screenshot of the full log entry.

[chickwebb]

@anon47916022

Are you using any of the browser navigation buttons when editing (e.g. back/forward buttons)? That's been known to corrupt rules.

When you say erase, do you mean you use the trash can icon to delete the action?

Yeah, no, never. And by erase I mean the "Erase IF Expression THEN" button on the condition actions editing page. Here's the screenshot.

[bravenel]

@chickwebb

hit "Erase", and get that error.

I'm able to reproduce this. Will put in a fix for this to be in the next release.

Incidentally, you can get around this error by not using Erase Expression until the next release. You can use Edit Expression to accomplish the same thing, by removing each of the expression elements. Or, you can simply delete the IF-THEN action itself, and create a new one in its place.

[chickwebb]

Thanks, @bravenel, for the quick response and fix. I'll try the workaround.

[chickwebb]

I discovered another way to make this happen, unfortunately. I started adding an IF/THEN, added one pre-existing Condition, and then realized that I had added the wrong one. When I clicked on the "Cancel this action" button, RM threw an exception. Afterwards, the Rule is corrupted and you can't do anything further with Conditional statements w/o causing further corruption or triggering the error again. Details of the errror attached.

[bravenel]

That's weird. I will look into it.

[neonturbo]

@chickwebb

I discovered another way to make this happen, unfortunately.

I had this exact same thing yesterday. I thought I had accidentally clicked the back arrow and corrupted the rule.

But thinking back, it was pretty much like you said. I was editing an If/Then, and I canceled because I changed my mind about what I wanted to do.

Also like you, the rule was permanently corrupted. It was there, you could access it from Apps and see everything I had done to that point, but I could no longer edit any of the actions in any shape or form.

[bravenel]

I can reproduce this. It's actually pretty much the same error as before.

[chickwebb]

I updated to the latest this morning and spent some time beating on the editing functions for conditions and nothing broke. Looks good @bravenel. Thanks.