Skip to content
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

Cookie is not allowed #414

Closed
joshhopkins opened this issue Feb 5, 2021 · 6 comments
Closed

Cookie is not allowed #414

joshhopkins opened this issue Feb 5, 2021 · 6 comments

Comments

@joshhopkins
Copy link

Would appreciate any insight into this: nhost/nhost-js-sdk#49

@joshhopkins joshhopkins changed the title Cookie not allowed Cookie is not allowed Feb 5, 2021
@joshhopkins
Copy link
Author

I had a quick look here at it appears that there something odd going on with validation. See output:

[Error [ValidationError]: "cookie" is not allowed] {
  _original: { cookie: true },
  details: [
    {
      message: '"cookie" is not allowed',
      path: [Array],
      type: 'object.unknown',
      context: [Object]
    }
  ]
}

@joshhopkins
Copy link
Author

joshhopkins commented Mar 6, 2021 via email

@elitan
Copy link
Contributor

elitan commented Mar 6, 2021

Strange, the code you link to do allow for the cookie property. Anything else in the hbp logs?

@joshhopkins
Copy link
Author

Ok, still testing, but I think I've finally traced it down. At some point I set ANONYMOUS_USERS_ENABLE=TRUE, which the nhost-js-sdk client doesn't handle yet. Understand this feature is experimental, so it's my fault. At some point I'd imagine the cookie property will be ignored in the case that useCookies: false.

@uthpalax
Copy link

uthpalax commented Mar 7, 2021

Okay I ran in to the same issue. I am too using nhost-js-sdk v3.

Update Hasura Backend Plus to 2.2.4 works - https://github.com/nhost/hasura-backend-plus/releases/tag/v2.2.4

In your local machine you can update HBP to 2.2.4 by updating the config.yaml inside the nhost directory and re-running nhost dev.

@elitan
Copy link
Contributor

elitan commented Mar 25, 2021

Upgrading seems to solve this issue.

@elitan elitan closed this as completed Mar 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants