-
-
Notifications
You must be signed in to change notification settings - Fork 131
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
undefined method `symbolize_keys' for Warden::JWTAuth:Module (NoMethodError) #159
Comments
Saw this after posting it myself, I have provided more details here. If anyone could help. |
For now lock you dry-configurable version to 0.9. I'll take a look as soon as possible. |
Fixed. It was a regression in dry-configurable and it has been fixed there. I've released v0.4.1 of warden-jwt_auth (which is the core engine for devise-jwt) depending on a version at least equal that the one containing the fix. So, in order to fix it for devise-jwt users, you just need to update warden-jwt:
|
Hold on, there're still some issues to be resolved. So keep with the version of dry-configurable locked. I'll report on news. |
Still seeing the following error when I don't freeze dry-configurable
|
Well I'm new to ruby on rails, however in my case you can fix that error by replacing the file value by [['POST', %r{^/login$}]] in:
and value by [['DELETE', %r{^/logout$}]] in:
However, I don't know what consequences it has on the proper functioning of the gem. The error comes from this method in the file
when the input variable equals undefined, it loads the null value giving the following error
|
As it's taking longer than expected to be fixed upstream in dry-configurable, I have released a new version of warden-jwt_auth 0.4.2 which locks itself dry-configurable version. This way, once it's updated there I'll just release a new version and it'll be transparent for the user. So, to fix it when using devise-jwt, just run |
Please, for a bug report fill in the following template. Before that, make sure to read the whole README and check if your issue is not related with CORS.
Feature requests and questions about
devise-jwt
are also accepted. It isn't the place for generic questions about usingdevise
with an API. For that, read our wiki page or ask somewhere else like stackoverflowExpected behavior
Actual behavior
/Users/reza/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/warden-jwt_auth-0.3.6/lib/warden/jwt_auth.rb:38:in `block in <module:JWTAuth>': undefined method `symbolize_keys' for Warden::JWTAuth:Module (NoMethodError)
Steps to Reproduce the Problem
gem 'devise'
andgem 'devise-jwt', '~> 0.5.9'
to Gemfile, then run bundlebundle exec rake secret
Debugging information
Provide following information. Please, format pasted output as code. Feel free to remove the secret key value.
devise-jwt
in use: '~> 0.5.9'rails
in use: 6.0.2.1Devise::JWT.config
Warden::JWTAuth.config
Devise.mappings
The text was updated successfully, but these errors were encountered: