Picovoice Console Issue: Email validation pattern is wrong
See original GitHub issueMake sure you have read the documentation, and have put forth a reasonable effort to find an existing answer.
Expected behaviour
Using the +
symbol in emails is allowed as per the email standards.
Actual behaviour
The +
symbol is not allowed in emails. There are probably other symbols that are wrongly blacklisted also.
Steps to reproduce the behaviour
Attempt to sign up with an email address that includes the +
symbol.
Issue Analytics
- State:
- Created a year ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Picovoice Console Issue: Error when using a German Rhino ...
I'm currently testing Picovoice for the development of a Flutter app. I created a Rhino model in English and loaded it into my...
Read more >FAQ | On-device Voice Recognition - Picovoice Docs
Voice AI models can be instantly trained on the Picovoice Console's type-and-train user interface and downloaded immediately. How do you collect user data?...
Read more >6 mistakes you're probably making with email validation - Loqate
6 mistakes you're probably making with email validation · Mistake 1 - Making people enter their address twice · Mistake 2 - Not...
Read more >Creating Great Voice Apps for Real Users - Springer Link
For information on translations, please e-mail ... Chapter 3: Running a Voice App—and Noticing Issues ............................ ... Engagement Patterns .
Read more >On-device Wake Word Detection Powered By Deep Learning
Developers can train custom wake word models using Picovoice Console. ... OnWakeWordDetected); } catch (Exception ex) { // handle porcupine init error }....
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 FreeTop 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
Top GitHub Comments
This issue has been resolved.
OK. This makes sense. We will work on this and get this fixed in the next couple of weeks