hub.alert() crashes QuickApp with "Wrong parameter type, string required. Provided param 'false' is type of boolean"

[pvandamcom 1]

I discovered a critical regression in the 5.192.6 beta firmware when using hub.alert("email", …) from QuickApps.
 

**Symptom

Calling

 

Please login or register to see this code.

(4 parameters – the most common syntax in many of my existing QuickApps) immediately crashes the QuickApp with:

 

Please login or register to see this code.

The QuickApp stops completely (polling stops, no more logs until manual restart).

Works perfectly on stable 5.190.39 and earlier.

Workaround is to add a string to parameter 4 instead of false.

[Sankotronic 2,370]

Hi @pvandamcom,

 

Please check here for changes regarding sending e-mails:

As you can see from above quick app hub.alert function is changed and there is no boolean parameter. You need to correct all your code and replace boolean parameter with e-mail subject.

[m.roszak 763]

To be honest, it never was any bool arg there in QuickApps - it was just ignored in the past.

[pvandamcom 1]

Thanks for this reference, I missed that.

This is quite a change, I typically use 6 (scenes) or 4 parameters based on documentation I could find.
And concluded the following order:

1.  type

2. user

3. messagebody

4. messagetopic

5. priority

6. sound

 

Last 2 could be ignored, but learned that 5 needed to be "" and 6 false.

 

Seems that the formal way is now:

scenes - 5 parameters, --> 3 is body, 4 is priority, 5 is Subject?

QA's - 4 parameters, --> 3 is body, 4 is messagesubject