-
Notifications
You must be signed in to change notification settings - Fork 246
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
Error: "DOMException [InvalidCharacterError]: Invalid character" on fresh install #1474
Comments
Hi @ConsM. Thank you for reporting these problems. I'm able to reproduce the first issue with logging into Shopify, but I'm unable to reproduce the second 500 error. Could you give some more information about your environment? What version of Node are you using? |
Hi @blittle, thanks for getting back. |
Hmmm, I'm still unable to reproduce the problem. Looking at the stack trace though, it seems as though something is breaking from a signed cookie that is being sent. Try loading |
spot on ! What is the actual cause though ? |
You probably have a cookie set at Though I think we should probably handle malformed cookies more gracefully with a 400 level error instead of 500. |
Assuming there's nothing private in the cookie, would you mind sending me the cookies set on |
sure, have created a secret one - how/where should i share it ? |
Maybe if you tag my GH user in a comment on the gist it will notify me? |
@ConsM got it! Thank you! |
The first part of this issue is now resolved in 2023.10.1 |
What is the location of your example repository?
No response
Which package or tool is having this issue?
Hydrogen
What version of that package or tool are you using?
Latest
What version of Remix are you using?
No response
Steps to Reproduce
npm create @shopify/hydrogen@latest
Then run
npm run dev
, accessedlocalhost:3001
and got the below errorHave also tried with my shopify credentials in the
.env
got the same error.Expected Behavior
Would expect a fresh install to work OOB
Actual Behavior
Server is returning 500
The text was updated successfully, but these errors were encountered: