HTTP 500's aren't handled when using the graph API about koala HOT 5 CLOSED

Hey,

It definitely shouldn't be doing that. I'll take a look at that soon.

Alex

from koala.

I'm in the process adding error handling for 500 responses and they should be up within the next few days. Do either of you have example Facebook URLs that currently return 500 responses that I can refer to for testing purposes?

from koala.

This URL should error out. https://graph.facebook.com/search?q=e3&type=post&since=2010-06-16T21:02:02%2b0000&until=2010-06-16T21:04:06%2B0000&limit=33

Side note: this is related to a bug on their side where the graph API returns an HTTP 500 in some cases if you provide a limit parameter greater than the available results.

from koala.

Thanks for the URL dacort.

I pushed a fix to master that raises an APIError for any server error response codes (500 or greater.) I haven't run into this problem myself, but I'm pretty sure Koala without this patch would have returned nil given the response from the broken URL above. The search URL returned an empty string for the body, which when parsed by API#api, would return [][0], the first element of an empty array, which is nil.

dacort, maybe you can take the patch for a spin in your app and let us know how it goes?

from koala.

Sounds like the issue is resolved; closing.

from koala.