Rescued errors come back with all nil values?

[gregblass]

Rescued errors come back with all nil values?

[ckornaros]

@gregblass The problem seems to be on version 3.2.0. I update to the last 3.3.3 and the error is correctly parse and available to let you handle errors depending on status, title or detail (or anything you want) 👍

[amro]

Glad to hear it’s the issue that was already fixed 👍🏽

[ckornaros]

@gregblass Yes I have the same issue. On debug mode I'm able to see the "real" reason of the exception but Gibbon seems to have a issue to parse the error.

[gregblass]

In some cases, you need to know what those errors are (if someone is unsubscribed). What is the issue with properly parsing error responses?

…

On Wed, Apr 8, 2020 at 5:10 AM Christos Kornaros ***@***.***> wrote: @gregblass <https://github.com/gregblass> Yes I have the same issue. On debug mode I'm able to see the "real" reason of the exception but Gibbon seems to have a issue to parse the error. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#294 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACEK5ZYL7N23KTUHFHR6JDRLQ5RZANCNFSM4MDNMVXA> .

[gregblass]

Really the core of my issue is finding out if the user is unsubscribed. Does anyone have a recommended way of doing that? I can't seem to see the details any of the errors coming back.

[gregblass]

Nevermind, I was able to easily find this in the Mailchimp API documentation:

https://mailchimp.com/developer/guides/manage-subscribers-with-the-mailchimp-api/

Just needed to go to sleep 😆

If there's anything I can do to potentially contribute here on the error parsing, I'm using this for two projects - and in some particular cases, it would be very useful to see what the errors are in cases where they're coming back as nil values.

I'm assuming that the issue is complex though?

[amro]

This may not be too tricky to figure out. I’ll try to take a look soon. Can you confirm how to repro? Just trigger a 404 by hitting a nonexistent api endpoint?

[gregblass]

Let me remember which ones were doing it again. It may actually be triggered by trying to do stuff on unsubscribed list members...in which case...just check first. So it may actually not be an issue after all.

I'll confirm this and circle back.