-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
#<IndexError: string not matched> after second sign_in request with postgres #1052
Comments
@dikey94 are you sure that your tokens column is JSON? See this search result: Sounds like maybe you have a column that's the wrong type? |
I'm sure. Here is a simple users table preview:
|
@dikey94 what database are you using to back your project? |
It's a docker version of postgres:10.1 |
It's a duplicate of #121 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello everyone,
I'm new in devise + token auth solution so please bear with me.
I noticed a strange behavior - the second sign_in request gives me 500 Internal Server Error - "#<IndexError: string not matched>". When I manually update tokens column and set it to null everything works fine.
Full response:
Gemfile:
Thanks for any support.
The text was updated successfully, but these errors were encountered: