You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 14, 2025. It is now read-only.
Despite this issue being closed in April of 2018, something has changed since then, and it does not work. I've done this setup two times total and followed the instructions to the letter with a great attention to detail and it ends with the error "undefined" when you select the "Request Unicorn".
I can take the auth token from the /ride.html page to the API gateway > authorizers > paste as auth header > test and I get a 200 response code all day long. got this both times i finished the setup.
there's one thing in the setup that has changed. the setup says to use Node.js 6.10. but that is no longer available as an option. the first time i selected node.js 12.x and it didnt' work. the second time I selected node.js 10.x. still doesn't work.
I've seen all of what @mikedeck has had to say, and I can assure that I have spelled everything to the T. Mike has suggested that perhaps the function is named something different than RequestUnicorn. I can assure this isn't the case. For every single item in the module, I copied and pasted, and made sure there were no extra characters or spaces anywhere.
Mike makes mention of an invalid Authorization header at the URL at the end of this sentence(s), but I don't know how to make sure the same token I copied is actually getting passed in the Autorization HTTP header on the POST request made, because that's what the function(s) of the module(s) is supposed to do... take a logged in user's auth, then pass to the lambda functions with the cognito user pool and get a ride. here #97 (comment)
HELP?
*note: the word occurred is misspelled "An error occured..."
The text was updated successfully, but these errors were encountered:
*an error occurred when requesting your unicorn: undefined
From https://aws.amazon.com/getting-started/hands-on/build-serverless-web-app-lambda-apigateway-s3-dynamodb-cognito/
Despite this issue being closed in April of 2018, something has changed since then, and it does not work. I've done this setup two times total and followed the instructions to the letter with a great attention to detail and it ends with the error "undefined" when you select the "Request Unicorn".
I can take the auth token from the /ride.html page to the API gateway > authorizers > paste as auth header > test and I get a 200 response code all day long. got this both times i finished the setup.
there's one thing in the setup that has changed. the setup says to use Node.js 6.10. but that is no longer available as an option. the first time i selected node.js 12.x and it didnt' work. the second time I selected node.js 10.x. still doesn't work.
I've seen all of what @mikedeck has had to say, and I can assure that I have spelled everything to the T. Mike has suggested that perhaps the function is named something different than RequestUnicorn. I can assure this isn't the case. For every single item in the module, I copied and pasted, and made sure there were no extra characters or spaces anywhere.
Mike makes mention of an invalid Authorization header at the URL at the end of this sentence(s), but I don't know how to make sure the same token I copied is actually getting passed in the Autorization HTTP header on the POST request made, because that's what the function(s) of the module(s) is supposed to do... take a logged in user's auth, then pass to the lambda functions with the cognito user pool and get a ride. here #97 (comment)
HELP?
*note: the word occurred is misspelled "An error occured..."
The text was updated successfully, but these errors were encountered: