Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
SignUp Screen withAuthenticator: No errors are displayed upon submitting incorrect form inputs
See original GitHub issueDescribe the bug
I am using the withAuthenticator HOC and I realized that no error messages are displayed when an input field is incorrect (wrong password format, username not available…)
I actually had to add “(8 characters min)” to the password label, otherwise users would keep on trying to sign up (with short password) without knowing what’s not working
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
React Authenticator form errors not showing up #3528 - GitHub
I wrap my App component with Authenticator in the most basic way: ... no form errors show (on incorrect credentials, missing signup field, ......
Read more >Login form implemented with Amplify is not applied styling
I am trying to implement login form with React and withAuthenticator() of Amplify in reference to a document of AWS(https://aws-amplify.github.
Read more >Common questions about the Microsoft Authenticator app
Q: I'm trying to sign in and I need to select the number in my app that's displayed on the sign-in screen, but...
Read more >Problem Solving Login Issues with Two-Factor Authentication
No. You can register for two-factor authentication on either Console or Author site. ... This error means that when your account was set...
Read more >Customizing the authentication experience of Amplify's ...
I want the user to enter their name so that the app can greet them when they login. I also don't need to...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks @amhinson, it looks like adding
keyboardShouldPersistTaps='handled'to theScrollViewcomponent fixed the error on the SignUp screen. I will submit a PR!Ah interesting! This looks like it might be an issue with the
ScrollViewused here, specifically thekeyboardshouldpersisttapsproperty. Maybe we can experiment with usinghandledinstead of the default (never)?