Closed jamesladd closed 10 years ago
Can you verify that you're using v 0.1.3 of the gem? There was an issue in previous versions where a2z was depending on any version of the jeff gem, and it was updated without me knowing to no longer assign the key value in the same way. The 0.1.3 update should have fixed that by specifying a specific version of the jeff gem.
Hey Matt, Due to my timeframes I went with another gem, will circle back when I can and check on your again as it looks very complete & more useful
On Sat, Jul 5, 2014 at 1:08 AM, Matt Huggins notifications@github.com wrote:
Can you verify that you're using v 0.1.3 of the gem? There was an issue in previous versions where a2z was depending on any version of the jeff gem, and it was updated without me knowing to no longer assign the key value in the same way. The 0.1.3 update should have fixed that by specifying a specific version of the jeff gem.
— Reply to this email directly or view it on GitHub https://github.com/mhuggins/a2z/issues/11#issuecomment-48053917.
Cool, no worries. I'm going to close this for now then, but please reopen if you try again and still have issues!
$ rails c Loading development environment (Rails 4.1.1) 2.1.2 :001 > config = YAML.load_file(Rails.root.join('config', 'amazon.yml')) => {"key"=>"your_key", "secret"=>"your_secret", "tag"=>"your_tag"} 2.1.2 :002 > client = A2z::Client.new(config) NoMethodError: undefined method `key=' for #A2z::Client:0x00000004fd4068
Why is key= undefined? and yet your build is passing?