Incompatible with devise because route helpers include configuration

[technicalpickles]

We've been using this gem for awhile, and at some point noticed that in development, the first request to need an authetnicated session would always fail with Warden::NotAuthenticated (:default user is not logged in). We traced this back to Devise not configuring warden until the routes are finalized: https://github.com/heartcombo/devise/blob/43800b4b8550d1249ab049a94ee7c16e243551a1/lib/devise/rails/routes.rb#L9-L23

module Devise
  module RouteSet
    def finalize!
      result = super
      @devise_finalized ||= begin
        if Devise.router_name.nil? && defined?(@devise_finalized) && self != Rails.application.try(:routes)
          warn "[DEVISE] We have detected that you are using devise_for inside engine routes. " \
            "In this case, you probably want to set Devise.router_name = MOUNT_POINT, where "   \
            "MOUNT_POINT is a symbol representing where this engine will be mounted at. For "   \
            "now Devise will default the mount point to :main_app. You can explicitly set it"   \
            " to :main_app as well in case you want to keep the current behavior."
        end

        Devise.configure_warden!
        Devise.regenerate_helpers!
        true
      end
      result
    end
  end
end

We confirmed that disabling this gem fixed the problem. I suspect there are other gems that could be affected which have configuration done in route helpers... activeadmin comes to mind as an example.