You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When user receives an e-mail with unlock link, clicking on it renders the unlock page with error "Unlock Token is invalid". Below is the smallest spec that I was able to make to reproduce the issue:
require"spec_helper"describeUsers::UnlocksControllerdobefore{request.env["devise.mapping"]=Devise.mappings[:user]}it"GET #show unlocks user if token is valid"douser=FactoryGirl.create:useruser.lock_access!email_token=Devise::Mailer.deliveries.last.body.match(/unlock_token=([^"]+)/)[1]get:show,unlock_token: email_tokenuser.reload.access_locked?.should == falseendend
1) Users::UnlocksController GET #show unlocks user if token is valid
Failure/Error: user.reload.access_locked?.should == false
expected: false
got: true (using ==)
# ./spec/controllers/users/unlocks_controller_spec.rb:13:in `block (2 levels) in <top (required)>'
I willing to bet that I am doing something wrong, but I am unable to understand what exactly. The devise source has no obvious omissions and the tests seem legit. Any ideas? Thanks in advance for your time and attention.
Using devise 3.4.1
The text was updated successfully, but these errors were encountered:
Please use the mailing list or StackOverflow for questions/help, where a wider community will be able to help you. We reserve the issues tracker for issues only.
When user receives an e-mail with unlock link, clicking on it renders the unlock page with error "Unlock Token is invalid". Below is the smallest spec that I was able to make to reproduce the issue:
Devise config:
I willing to bet that I am doing something wrong, but I am unable to understand what exactly. The devise source has no obvious omissions and the tests seem legit. Any ideas? Thanks in advance for your time and attention.
Using devise 3.4.1
The text was updated successfully, but these errors were encountered: