You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Confirmed the issue and the suggested fix made locally solves it. The alternative is to send a message to this node which has an object as the payload. e.g. using a Paylod of type 'JSON' and setting the value to '{}' or with your own, populated object.
FYI, the issue is that the code tests whether a payload exits and if if it does, the assumption is that the payload is of type 'object'. In my case the payload had a simple string. Attempting to add the 'capturedImg' property to a string or boolean fails as they are not a Javascript Object type.
I think the author is attempting to preserve the inbound message by adding a new property to hold the image. This is probably best handled with an option on the node itself which controls whether the outbound message payload is replaced with the image or the additional 'capturedImg' property is added to it. For the latter, the user would have to ensure that the incoming message had an object as the payload.
In the latest version this node doesn't seem to work. this line gives an error:
After changing it to :
msg.payload = buffer;
the flow starts working again.
The text was updated successfully, but these errors were encountered: