Skip to content

server errors show up as empty ParseProtocolError #60

Closed
ericcj opened this Issue Jan 22, 2013 · 4 comments

2 participants

@ericcj
ericcj commented Jan 22, 2013

parsed is sometimes nil on server errors in which case you get a blank exception

#<Parse::ParseProtocolError: : >

from

    if response.status >= 400
      raise ParseProtocolError.new(parsed)
    end
@adelevie
Owner
@ericcj
ericcj commented Jan 22, 2013

i don't totally understand which response we're getting from them to get in this state. it's something with an error code but empty body since

ruby-1.9.2-p0 :037 > JSON.parse('')
=> nil

@adelevie
Owner
adelevie commented Apr 8, 2013

@ericcj is this still occurring?

@ericcj
ericcj commented Apr 10, 2013

i believe so. the last one we encountered was on march 14th:

Parse::ParseProtocolError: :
[GEM_ROOT]/gems/parse-ruby-client-0.1.11.ericcj.12/lib/parse/client.rb:61:in request'
[GEM_ROOT]/gems/parse-ruby-client-0.1.11.ericcj.12/lib/parse/object.rb:122:in
save'

@ericcj ericcj closed this Apr 22, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.