RailsでコントローラーからApplicationControllerのメソッドにアクセスできない

Question

RailsをAPIとして使っています。devise token authでトークン認証を導入し、ログイン認証は問題なくできています。しかし、リソースにアクセスしようとすると、ApplicationControllerに存在するメソッドにサブコントローラーからアクセスできず、NoMethodErrorとなってしまいます。
skip_before_action :verify_authenticity_tokenをコメントアウトするしないで、ログインができるできない、リソースにアクセスできるできないが変わってくるようなのですが、どう対処したら良いのでしょうか。

ruby 2.6.6
rails 6.0.3.4
devise 4.7.3
devise_token_auth 1.1.3

エラーメッセージ
NoMethodError in SubController#index
undefined method `methodA' for #<SubController:0x0000559c2a82e8c8>

Extracted source (around line #428):

  lambda do |target, value, &block|
    target, block, method, *arguments = expand(target, value, block)
    target.send(method, *arguments, &block)
  end
end

class ApplicationController < ActionController::API
  include DeviseTokenAuth::Concerns::SetUserByToken
  skip_before_action :verify_authenticity_token #コメントアウトすると、リソースにアクセスできるが、ログインできない
  before_action :authenticate_api_user!

  protected
  def methodA
    # 略
  end
end

class SubController < ApplicationController
  before_action :methodA, only: [:index]
  
  def index
    # 略
  end

end

DeviseTokenAuth.setup do |config|
  # By default the authorization headers will change after each request. The
  # client is responsible for keeping track of the changing tokens. Change
  # this to false to prevent the Authorization header from changing after
  # each request.
  config.change_headers_on_each_request = false

  # By default, users will need to re-authenticate after 2 weeks. This setting
  # determines how long tokens will remain valid after they are issued.
  config.token_lifespan = 2.weeks

  # Limiting the token_cost to just 4 in testing will increase the performance of
  # your test suite dramatically. The possible cost value is within range from 4
  # to 31. It is recommended to not use a value more than 10 in other environments.
  config.token_cost = Rails.env.test? ? 4 : 10

  # Sets the max number of concurrent devices per user, which is 10 by default.
  # After this limit is reached, the oldest tokens will be removed.
  # config.max_number_of_devices = 10

  # Sometimes it's necessary to make several requests to the API at the same
  # time. In this case, each request in the batch will need to share the same
  # auth token. This setting determines how far apart the requests can be while
  # still using the same auth token.
  # config.batch_request_buffer_throttle = 5.seconds

  # This route will be the prefix for all oauth2 redirect callbacks. For
  # example, using the default '/omniauth', the github oauth2 provider will
  # redirect successful authentications to '/omniauth/github/callback'
  # config.omniauth_prefix = "/omniauth"

  # By default sending current password is not needed for the password update.
  # Uncomment to enforce current_password param to be checked before all
  # attribute updates. Set it to :password if you want it to be checked only if
  # password is updated.
  # config.check_current_password_before_update = :attributes

  # By default we will use callbacks for single omniauth.
  # It depends on fields like email, provider and uid.
  # config.default_callbacks = true

  # Makes it possible to change the headers names
  config.headers_names = {:'access-token' => 'access-token',
                          :'client' => 'client',
                          :'expiry' => 'expiry',
                          :'uid' => 'uid',
                          :'token-type' => 'token-type' }

  # By default, only Bearer Token authentication is implemented out of the box.
  # If, however, you wish to integrate with legacy Devise authentication, you can
  # do so by enabling this flag. NOTE: This feature is highly experimental!
  # config.enable_standard_devise_support = false
end

Comments

[maisumakun]

> ApplicationControllerに存在するメソッドにサブコントローラーからアクセスできず、NoMethodErrorとなってしまいます。

エラーメッセージを「そのまま」書いていただけないでしょうか？

[退会済みユーザー]

ChromeのNetworkから確認できたエラーメッセージを追加しました。

[退会済みユーザー]

ちなみに、methodAをサブクラス側に記述すると、問題なくレスポンスが帰ってきます。

Answer 1

before_action :authenticate_api_user!をサブクラス側に移動させて対応しました。
どうやら、 skip_before_action :verify_authenticity_tokenと一緒にスーパークラスに記載していた点で相性が悪かったようです。