-
Notifications
You must be signed in to change notification settings - Fork 37
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
ActionController::InvalidAuthenticityToken for Cloudtasker::WorkerController#run #40
Comments
just to be clear/explicit: because edit: also this only happens in development environment, eg in production because of eager loading the |
@eLod thanks for raising this issue. It looks weird to me that |
well, i just checked, with a bare new rails app, only change is adding the cloudtasker gem: with rails 5
with rails6
|
upon further checking it seems our active admin & devise & devise_authy initialization process is causing the |
well, its active_admin and devise, the routes include something like i can confirm, with the bare new rails app, adding activeadmin and devise latest versions, and placing rails5
rails6
|
oh i just found, most likely this somewhat cryptic pr #36 is trying to solve the same issue |
Going to do more testing on my side. Looks like PR #36 is the way to go in the end. |
i really feel #36 is the wrong "solution", it keeps subclassing |
I'll rewrite this PR. We can just get rid of ApplicationController I suppose - it's fairly useless. |
sure that is also a solution, most likely the best one |
This issue has been fixed in the following releases:
|
Rails 5.2.2, gem version 0.11.
Cloudtasker::WorkerController
uses an ambigious superclass, ifCloudtasker::ApplicationController
is not loaded it simply subclasses::ApplicationController
, e.g. i can reproduce in console:The text was updated successfully, but these errors were encountered: