title: invalid salt (BCrypt::Errors::InvalidSalt)
body: <p>Since upgraded to Ruby 2.2.0 I get the following message in my tests:</p>
  
  <pre><code>invalid salt (BCrypt::Errors::InvalidSalt)
  </code></pre>
  
  <p>I didn't find any upgrade notice helping me to understand the problem. I'm using Rails 4.1.8 and Sorcery 0.8.6.</p>
  
  <p>Anybody else having this problem?</p>
  
  <p>MORE Details:</p>
  
  <p>I'm using Sorcery and not Devise. The encrypted data is the password.
  It all started in Cucumber tests, in 2 cases:
  When I used to send the @user to the mailer to prepare the data for the mails. Here was the code:</p>
  
  <p>UserMailer.passphrase_reset_notification(@user).deliver</p>
  
  <p>Which generated the exception with the message I wrote in the initial message. As a workaround instead of sending the @user I sent the fields I needed and it worked. Here's the new code:</p>
  
  <p>UserMailer.passphrase_reset_notification(@user.name, @user.email).deliver</p>
  
  <p>But the second case is the sign up. It failed in dev and I had to add :salt to user_params to fix it. But it does not fix the thing in the test env. </p>
  
  <p>There's no stack trace, just that one liner message with the lines of my scenario leading to the error. </p>
  
  <p>And I press "Sign up"
        invalid salt (BCrypt::Errors::InvalidSalt)
        ./app/controllers/users_controller.rb:66:in <code>block in create'
        ./app/controllers/users_controller.rb:64:in</code>create'
        ./app/controllers/application_controller.rb:120:in <code>scope_current_tenant'
        ./features/step_definitions/web_steps.rb:53:in</code>/^(?:|I )press "([^"]*)"$/'
        features/users/sign_up.feature:149:in `And I press "Sign up"'</p>
  
  <p>I removed the "null: false" for the field "salt" in the user table, as suggested by a community member in a post on a more or less similar issue, it didn't help either. </p>
  
  <p>My main question is still the same: what the Ruby new version (2.2.0) has to do with this? And what might be the other surprises if I upgrade the prod?</p>