Closed tinhphamvan closed 1 year ago
lasttime i used 3.9.0 and it works perfect
I knew why, dependencies must be update to faraday 2.0 instead of 1.10.2 Pls verify!!!
Yes, the latest release was updated to support faraday 2.x and in doing so no longer supports 1.x. This should have been a major version as it's a breaking change. My apologies. The next release will be 4.0.0 with call out of breaking change of faraday dependency
It might be worth yanking the 3.17.0 gem from rubygems.org, if it's a known-broken release. Otherwise people (like me! :smile:) with a Gemfile constraint of gem 'xero-ruby', '~> 3.0'
might upgrade to 3.17.0 and run into this problem.
It might be worth yanking the 3.17.0 gem from rubygems.org, if it's a known-broken release. Otherwise people (like me! 😄) with a Gemfile constraint of
gem 'xero-ruby', '~> 3.0'
might upgrade to 3.17.0 and run into this problem.
Yes, it's quite annoying! what i have done when update from 3.9 --> 3.17 is: Upgrade:
Yeah, I wasted far too much time debugging this because I have other dependencies holding back Faraday
Thank you @tinhphamvan for picking this up, we've pulled the 3.17.0 gem now from rubygems. If you want to keep Faraday 2.0, please use gem version >= 4.0.0. @gravitystorm @HashNotAdam
Thank you @pumpkinball !
I tried upgrade to 3.17 but i got
ArgumentError: wrong number of arguments (given 4, expected 3) from /usr/local/bundle/gems/faraday-1.10.2/lib/faraday/request/authorization.rb:48:in
initialize'` when calling xero_client.last_connectionBecause of faraday version or sth?? Can you guys help me take a look?