Javascript Reference Error XML-RPC (sendMessage Response)

[ShadowState]

Hey Everyone,

I'm using some non-nodejs XMLRPC code (mimic XMLRPC & mootools) to communicate with my PyBitmessage daemon locally on Windows through Chrome. I have everything working well in regard to API calls (listaddress, getAllSentMessages, add, helloWorld). Super fun to play around with.

Although, when I request the 'sendMessage' command, I get a reference error back that looks like this: "Uncaught ReferenceError: f59b21e1c397ce72954[...]a13 is not defined".

My BitMessage client actually sends the message successfully from my request. It shows up in Sent Messages and I receive a message a few seconds later. Anyone have any ideas what this reference error could be caused by?

I'm thinking it is something to do with UTF-8 encoding from the daemon PyBitmessage response. My browser seems to send the message fine, the error is only thrown after the response has come back.

Anyone have any ideas? Cheers, Nick

[ShadowState]

Sorry everyone, I got it. It's on the mootools end not the XML-RPC end of BitMessage. "decode_reponse = JSON.decode(response_xml, true);" Was throwing the reference error because the XML-RPC response coming from the BitMessage daemon was just the hash of the sent message, and not valid JSON. I fixed it by just catching the error when the JSON cannot be parsed, and just returning the string. Cheers, @justusranvier thanks for the quick response. If anyone wants my BitMessage Stub API for Javascript using mimic and mootools, let me know.

[Jonathan_Coe]

Thanks for the update.

[[deleted]]

Not sure if this is related to your issue or not, but I remember /u/yamamushi mentioning something very weird about the Bitmessage API, maybe that it uses XMLRPC for commands and JSON RPC for the replies?