devise_token_auth 1.1.0 installation fails with "undefined method 'devise' for User"

[drj17]

When posting issues, please include the following information to speed up the troubleshooting process:

• Version: 1.1.0
• Rails Version: 5.2.3
• Rails Stacktrace:

rake aborted!
NoMethodError: undefined method `devise' for User (call 'User.connection' to establish a connection):Class
/app/models/user.rb:8:in `include'
/app/models/user.rb:8:in `<class:User>'
/app/models/user.rb:3:in `<main>'
/config/routes.rb:2:in `block in <main>'
/config/routes.rb:1:in `<main>'
/config/environment.rb:5:in `<main>'
Tasks: TOP => db:migrate => db:load_config => environment
(See full trace by running task with --trace)

Given the current installation settings in the documentation, installation fails in a brand new rails project.

[vinhkq]

@drj17
You can add extend Devise::Models in User.rb Model.
It fixed for me.

[dks17]

This is Devise issue, but not the gem. And this is a Stack Overflow question.

ActiveRecord ORM was hard coded inside of the gem before. Now you must follow by Devise configuration.

  # ==> ORM configuration
  # Load and configure the ORM. Supports :active_record (default) and
  # :mongoid (bson_ext recommended) by default. Other ORMs may be
  # available as additional gems.
  require 'devise/orm/<%= options[:orm] %>'

Check also the gem doc.

[jeffjiang0613]

I have met with the same issue in version 1.1.0, when I change the devise_token_auth to previous version 1.0.0, it works.

[drj17]

I would argue this is not a devise issue because you cannot install this gem with the readme as is. Perhaps someone would like to make that pull request? I could do it one I get access to a computer

[reneclavijo]

I had the same issue, and just with 1.0.0 version works fine. If I use extend Devise::Models in User.rb raise an error with /auth/sign_in (creating sessions)

[CDimonaco]

The update to the latest version should be documented in a better way, the way to go is create an initializer for devise and load active record, like @drj17 said, the changelog of this gem does not mention the upgrade step, and does not mention the new devise dependency.

I think we should definitely put something in the installation documentation, or at least an 'upgrade' section in the gem docs.

[dkniffin]

Any progress on this? I'm running into the same issue. @Tiltorito I see you opened a PR but the tests were failing. To me it looks like the reason was an intermittent issue with Travis. You could try restarting the build and that might fix it, but I could be way off base.