We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It looks like signOutUser sets the access-token / uid / client as data when they should be set as headers. Relevant devise_token_auth docs: https://devise-token-auth.gitbook.io/devise-token-auth/usage
data
headers
The text was updated successfully, but these errors were encountered:
Bit by same, any fixes?
Sorry, something went wrong.
REPLACE3=' data: userSignOutCredentials, headers: userSignOutCredentials,'; ESCAPED_REPLACE3=$(printf '%s\n' "$REPLACE3" | sed -e 's/[\/&]/\\&/g'); sed -i.buk "234s/.*/$ESCAPED_REPLACE3/" node_modules/redux-token-auth/dist/actions.js rm node_modules/redux-token-auth/dist/actions.js.buk
Use this script with after install hook, is a monkey patch, but solves the problem.
No branches or pull requests
It looks like signOutUser sets the access-token / uid / client as
data
when they should be set asheaders
. Relevant devise_token_auth docs: https://devise-token-auth.gitbook.io/devise-token-auth/usageThe text was updated successfully, but these errors were encountered: