Gem Version dependency Issue about ruby-sdk HOT 6 OPEN

Hello - is it an option to upgrade Rails a point release or so? ActionMailer 4.1.6 should support a higher version of Mime-Types: https://rubygems.org/gems/actionmailer/versions/4.1.6

from ruby-sdk.

Are there any plans to update this gem to address this dependency issue? This question is two years old and this is still an problem.

from ruby-sdk.

What version of the SDK are you using? 4.0 removed the mime-type dependency: https://rubygems.org/gems/constantcontact/versions/4.0.0

If you need an older version for some reason, if it's possible for go from Rails 4.1.4 to 4.1.6 or later (assuming your problem is exactly the one above), the mime-type dependency conflict should also go away. Rails 4.1 is out of all support at this point.

from ruby-sdk.

I'm using 4.1.0 and rails 5.1.1. This is the error I'm getting:

Bundler could not find compatible versions for gem "json":
  In snapshot (Gemfile.lock):
    json (= 1.8.6)

  In Gemfile:
    constantcontact (~> 4.1.0) was resolved to 4.1.0, which depends on
      json (~> 2.1)

    fog was resolved to 1.40.0, which depends on
      json (< 2.0, >= 1.8)

    raygun4ruby was resolved to 2.3.0, which depends on
      json

    fog was resolved to 1.40.0, which depends on
      fog-vsphere (>= 0.4.0) was resolved to 1.10.0, which depends on
        rbvmomi (~> 1.9) was resolved to 1.11.2, which depends on
          json (>= 1.8)

    sdoc (~> 0.4.0) was resolved to 0.4.2, which depends on
      json (>= 1.7.7, ~> 1.7)

Running `bundle update` will rebuild your snapshot from scratch, using only
the gems in your Gemfile, which may resolve the conflict.

from ruby-sdk.

Oh, I see... so we went to json 2 a few releases ago as at the time, 1.x didn't look like it was still being developed. If I relax the dependencies to '>= 1.8' instead of '~> 2.1', you may be in luck here. If I force myself to use 1.8.x, My RSpec tests pass but that's as far as I got.

I'm no longer on the API team at Constant Contact, so I'm unsure when and if those changes can be more properly validated here and merged in, but if you are able to validate and issue a pull request it would be appreciated. I'll forward along to the team either way what the problem is here and apologies for the issues.

from ruby-sdk.

That did indeed solve the problem for me. I issued a pull request. Thank you for the suggestion.

from ruby-sdk.