-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deployment on heroku: alias_method 'current_user' undefined #29
Comments
heroku[web.1]: State changed from starting to crashed app[web.1]: from /app/vendor/bundle/ruby/2.6.0/gems/rack-2.0.7/lib/rack/builder.rb:55:in instance_eval' app[web.1]: from /app/vendor/bundle/ruby/2.6.0/gems/rack-2.0.7/lib/rack/builder.rb:55:in initialize'app[web.1]: from config.ru:in new' app[web.1]: from config.ru:in 'app[web.1]: from /app/vendor/bundle/ruby/2.6.0/gems/rack-2.0.7/lib/rack/builder.rb:49:in eval' app[web.1]: from /app/vendor/bundle/ruby/2.6.0/gems/rack-2.0.7/lib/rack/builder.rb:49:in new_from_string'app[web.1]: from /app/vendor/bundle/ruby/2.6.0/gems/rack-2.0.7/lib/rack/builder.rb:40:in parse_file' app[web.1]: from /app/vendor/bundle/ruby/2.6.0/gems/rack-2.0.7/lib/rack/server.rb:319:in build_app_and_options_from_config'app[web.1]: from /app/vendor/bundle/ruby/2.6.0/gems/rack-2.0.7/lib/rack/server.rb:219:in app' app[web.1]: from /app/vendor/bundle/ruby/2.6.0/gems/railties-5.2.0/lib/rails/commands/server/server_command.rb:27:in app'app[web.1]: from /app/vendor/bundle/ruby/2.6.0/gems/rack-2.0.7/lib/rack/server.rb:354:in wrapped_app' app[web.1]: from /app/vendor/bundle/ruby/2.6.0/gems/rack-2.0.7/lib/rack/server.rb:283:in start'app[web.1]: from /app/vendor/bundle/ruby/2.6.0/gems/railties-5.2.0/lib/rails/commands/server/server_command.rb:53:in start' app[web.1]: from /app/vendor/bundle/ruby/2.6.0/gems/railties-5.2.0/lib/rails/commands/server/server_command.rb:147:in block in perform'app[web.1]: from /app/vendor/bundle/ruby/2.6.0/gems/railties-5.2.0/lib/rails/commands/server/server_command.rb:142:in tap' app[web.1]: from /app/vendor/bundle/ruby/2.6.0/gems/railties-5.2.0/lib/rails/commands/server/server_command.rb:142:in perform'app[web.1]: from /app/vendor/bundle/ruby/2.6.0/gems/thor-0.20.3/lib/thor/command.rb:27:in run' app[web.1]: from /app/vendor/bundle/ruby/2.6.0/gems/thor-0.20.3/lib/thor/invocation.rb:126:in invoke_command'app[web.1]: from /app/vendor/bundle/ruby/2.6.0/gems/thor-0.20.3/lib/thor.rb:387:in dispatch' app[web.1]: from /app/vendor/bundle/ruby/2.6.0/gems/railties-5.2.0/lib/rails/command/base.rb:65:in perform'app[web.1]: from /app/vendor/bundle/ruby/2.6.0/gems/railties-5.2.0/lib/rails/command.rb:46:in invoke' app[web.1]: from /app/vendor/bundle/ruby/2.6.0/gems/railties-5.2.0/lib/rails/commands.rb:18:in <top (required)>'app[web.1]: from bin/rails:9:in require' app[web.1]: from bin/rails:9:in 'app[web.1]: => Booting Puma app[web.1]: => Rails 5.2.0 application starting in production app[web.1]: => Run rails server -h for more startup optionsapp[web.1]: Exiting |
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
I do see it in
https://github.com/rails-engine/notifications/blob/master/app/controllers/notifications/application_controller.rb
I am using the defaults forcurrent_user
andauthenticate_user!
could it be that it is getting loaded before devise?
The text was updated successfully, but these errors were encountered: