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
There are a couple of scenarios in which I get the following XML parse error:
MultiXml::ParseError: Start tag expected, '<' not found"
Firstly when trying to repeat an action like trying to create a subscriber with a customer ID that already exists. The workaround is for me to make sure that before I try and do Anything, I check that it hasn't already been done, but I'd really prefer RSpreedly to return me something sensible.
I'm not sure what the expected response should be in these cases, but my guess is that the api call is returning something other than XML.
I'd try and patch this myself, but I fear my Ruby-fu is too weak :(
EDIT:
I think this might actually just be a bug in response code handling? Here's the response object I get when creating an invoice with an invalid subscriber record - doing this call results in the XML parse error above:
#<HTTParty::Response:0x8 @parsed_response=nil, @response=#<Net::HTTPNotFound 404 Not Found readbody=true>, @headers={"server"=>["nginx"], "date"=>["Thu, 12 Apr 2012 16:23:55 GMT"], "content-type"=>["text/html"], "connection"=>["close"], "status"=>["404 Not Found"], "content-length"=>["0"], "x-runtime"=>["0.006309"]}>
The text was updated successfully, but these errors were encountered:
There are a couple of scenarios in which I get the following XML parse error:
Firstly when trying to repeat an action like trying to create a subscriber with a customer ID that already exists. The workaround is for me to make sure that before I try and do Anything, I check that it hasn't already been done, but I'd really prefer RSpreedly to return me something sensible.
The other (and far more worrying) scenario is when sending invalid payment details - e.g. the visa 4012888888881881 example from here: http://spreedly.com/manual/integration-reference/payments-api/pay-invoice
I'm not sure what the expected response should be in these cases, but my guess is that the api call is returning something other than XML.
I'd try and patch this myself, but I fear my Ruby-fu is too weak :(
EDIT:
I think this might actually just be a bug in response code handling? Here's the response object I get when creating an invoice with an invalid subscriber record - doing this call results in the XML parse error above:
The text was updated successfully, but these errors were encountered: