-
Notifications
You must be signed in to change notification settings - Fork 106
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
🐛 No localization for the error text if the email or password is wrong #418
Comments
|
Also, is this project being officially supported by anyone? @russellwheatley / @lesnitsky perhaps you know? |
@atreeon - here are the error codes we currently support: https://github.com/firebase/FirebaseUI-Flutter/blob/main/packages/firebase_ui_auth/lib/src/widgets/error_text.dart#L13-L36 If you wish, you could open a PR for the particular error code you wish to have language support. failing that, you can actually customise your own error codes following the instructions set out here: https://github.com/firebase/FirebaseUI-Flutter/blob/main/packages/firebase_ui_auth/lib/src/widgets/error_text.dart#L42-L54 |
Unfortunately I don't have the time to open a PR at the moment but maybe early next year. Keep open please (personally I'd have categorised this as a bug). |
Hello 👋, to help manage issues we automatically close stale issues. This issue has been automatically marked as stale because it has not had activity for quite some time. Has this issue been fixed, or does it still require attention?
Thank you for your contributions. |
Is there an existing issue for this?
What plugin is this bug for?
Firebase UI Auth
What platform(s) does this bug affect?
macOS
List of dependencies used.
firebase_core: ^3.6.0
firebase_auth: ^5.3.1
firebase_ui_auth: ^1.16.0
firebase_crashlytics: ^4.1.3
google_sign_in: ^6.2.1
firebase_ui_oauth_google: ^1.4.0
Steps to reproduce
Login with an incorrect email address.
Expected Behavior
After overriding every localization it seems that nothing sets the error message.
Actual Behavior
Additional Information
No response
The text was updated successfully, but these errors were encountered: