search

dabit3 / gatsby-auth-starter-aws-amplify

Starter Project with Authentication with Gatsby & AWS Amplify
MIT License
324 stars 400 forks source link

NOT ABLE TO SIGN UP #31

Open arhoy opened 4 years ago

arhoy commented 4 years ago

I have got the starter setup and after running gatsby develop I cannot sign up

Why is this happening and how come it is so difficult (impossible) to sign up? phone numbers tried 555 555 5555 555-555-6555 (555) -555-6555

error signing up... {code: "InvalidParameterException", name: "InvalidParameterException", message: "Invalid phone number format."} code: "InvalidParameterException" name: "InvalidParameterException" message: "Invalid phone number format." proto: Object

mtliendo commented 4 years ago

AWS (Cognito) expects a country code to be passed in as well ie +1 if you're in the US

full example +15555555555

arhoy commented 4 years ago

Ok thank you! Is there a way to change the error messages I am getting back? They are quite mystical. Also was wondering if there is some react hook demos/repos with Facebook and Google Auth, the docs are really killing me

mtliendo commented 4 years ago

Not that I know of. Even though Amplify is open source, it still injects data into AWS at the end of the day, so the error message you’re getting isn’t coming from Amplify, so much as it is Cognito—Amazon’s user service.

With regards to integrating google and Facebook, Nader also has videos up in case the docs need updating.

For Facebook sign in: https://youtu.be/F6ZPTKiEJx4

For google: https://youtu.be/eqDUSY9KHYE

Hope those help 😁 if not, feel free to open up an issue on the cli or tag me on Twitter (@mtliendo) and I’ll be happy to help out.

arhoy commented 4 years ago

Thanks for the youtube links I will check them out. As for your previous comment, how are people handling error message in real life? Because it is clearly a lot different than the alert message json string pop ups from the starter file 😁 I am looking for ways to modify that userflow

mtliendo commented 4 years ago

That's a good point. I'll dive a bit deeper this weekend and see if that error can be caught so it's not breaking the app. This'll take place over in the amplify/cli repo.