3.4.1 Causes 401: API Key Invalid

[GabeIsman]

3.4.1 Causes 401: API Key Invalid

[amro]

Hi Gabe, thanks for the bug report and sorry for the trouble. I’ll take a look at this in the morning.

…

On Oct 27, 2021, at 7:44 PM, Gabe Isman ***@***.***> wrote:  After upgrading to 3.4.1 today, I started getting errors from Mailchimp that looked like this #<Gibbon::MailChimpError: the server responded with status 401 @title="API Key Invalid", @detail="Your request did not include an API key.", @Body={:type=>"https://mailchimp.com/developer/marketing/docs/errors/", :title=>"API Key Invalid", :status=>401, :detail=>"Your request did not include an API key.", :instance=>"86f56459-56c1-e225-1bc7-169060c257ff"}, @raw_body="{\"type\":\"https://mailchimp.com/developer/marketing/docs/errors/\",\"title\":\"API Key Invalid\",\"status\":401,\"detail\":\"Your request did not include an API key.\",\"instance\":\"86f56459-56c1-e225-1bc7-169060c257ff\"}", @status_code=401> After doing some digging and trying the obvious things I noticed that the release had made some changes to the faraday basic_auth call. Confirmed that rolling back to 3.4.0 fixed the problem. Just undoing the change made to APIRequest in 902d61c was enough actually. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[amro]

@GabeIsman I'm going to yank v3.4.1. Can you please try 3.4.2? That should address this issue for you.

[GabeIsman]

Unfortunately my other dependencies are incompatible with faraday >= 1.0.0 so I can't easily test this out. I imagine it will resolve the issue though.

…

On Thu, Oct 28, 2021 at 9:36 AM Amro Mousa ***@***.***> wrote: @GabeIsman <https://github.com/GabeIsman> I'm going to yank v3.4.1. Can you please try 3.4.2? That should address this issue for you. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#305 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFKLSJ54ATQYLX6K6WZ37DUJFGUVANCNFSM5G3RAE3Q> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[amro]

No problem. Do you recall which dependencies caused issues for you? I’m wondering if I can drop versions on them without other trouble

[austinwalter]

I'm seeing this same issue too. I'm downgrading back to my previous version, but then I'll try v3.4.2 and see if that fixes it.

[amro]

3.4.2 should resolve it, yep. Please let me know if you run into trouble

…

On Sun, Nov 7, 2021 at 7:40 PM Austin Walter ***@***.***> wrote: I'm seeing this same issue too. I'm downgrading back to my previous version, but then I'll try v3.4.2 and see if that fixes it. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#305 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAEEBCE2P7BZLQX3SPZSN3UK4MBLANCNFSM5G3RAE3Q> .

[austinwalter]

v3.4.2 seems to be working. Thanks.