Deployment on heroku: alias_method 'current_user' undefined #29
Description
The integration works fine in development, but this is preventing my app from starting in heroku
I see that the codebase does define current user in the controller, but it seems to be breaking during the startup of the app after the build.
I am using devise 4.6.2, rails 5.2, ruby 2.6.0
2019-08-11T07:27:05.920574+00:00 heroku[web.1]: State changed from crashed to starting
2019-08-11T07:27:10.246313+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 23752 -e production`
2019-08-11T07:27:15.427833+00:00 heroku[web.1]: State changed from starting to crashed
2019-08-11T07:27:15.409030+00:00 heroku[web.1]: Process exited with status 1
2019-08-11T07:27:15.316165+00:00 app[web.1]: /app/vendor/bundle/ruby/2.5.0/gems/notifications-0.6.1/app/controllers/notifications/application_controller.rb:5:in `alias_method': undefined method `current_user' for class `Notifications::ApplicationController' (NameError)
I do see it in https://github.com/rails-engine/notifications/blob/master/app/controllers/notifications/application_controller.rb I am using the defaults for current_user and authenticate_user!
could it be that it is getting loaded before devise?