-
Notifications
You must be signed in to change notification settings - Fork 21
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
Invalid or unexpected token #9
Comments
Just to make sure: Have you fetched a token and saved it in the cookie-file? |
Try host |
Thank you, unfortunately it produces the same result |
If I try to use Auth Method "Cookie", there doesn't seem to be an issue. But as I understand, only the Proxy method would periodically refresh the cookie as needed (and that with the Cookie method, I need to go in and update it manually once in a while). |
I was able to trace the callstack but not to the line that creates the message "Invalid or unexpected token" (maybe because of nodejs/node#11865?)
|
I was able to figure this out, my investigation is documented here. It turns out my copy of npm package core-util-is had become corrupted and needed a reinstall. |
When using debug-level logging, nodered reports the following while trying to initialize Alexa. I'm not sure how to trace the "Invalid or unexpected token" error to a specific callstack:
Node-RED version: v2.0.5
Node.js version: v14.17.5
Linux 5.10.17-v7+ arm LE
"node-red-contrib-alexa-remote2-applestrudel": {
"version": "5.0.2",
"alexa-remote2": {
"version": "3.9.0",
"alexa-cookie2": {
"version": "3.4.3",
The text was updated successfully, but these errors were encountered: