-
Notifications
You must be signed in to change notification settings - Fork 107
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
🐛 [firebase_ui_auth] too many bugs #41
Comments
Thanks for the report @graemep-nz So the verification screen keeps going on as below: Same as above when using /cc @Lyokone @lesnitsky |
Did you provide SignInScreen(
actions: [
AuthStateChangeAction<UserCreated>((context, state) {
// perform post-registration logic here, for example – open a new screen
}),
],
);
There is a chance that something has changed in the underlying package or apple-specific configuration. An easy way to verify that everything is configured correctly is to create a dynamic link and try to handle it with
Please provide a reproducible example.
Localization-related issues will be handled a bit later since the localization team is a bit busy and slow to respond, so we're accumulating more labels so that we can get all translated in a single batch. It is easier for us to track each individual problem/bug under a separate issue, so I'd be grateful if you can submit several issues next time, instead of a single one with a list of problems. If something was fixed, but you are still able to reproduce it – feel free to reopen the previously submitted issue and leave a comment on what exactly is not working for you. Ideally, this comment should contain a code snippet/link to a repo (read more about minimal reproducible examples here). Very often something is not working because something is not configured properly or misused. These examples help a lot and speed up the process. |
I will reply in the near future, probably tomorrow. |
see also (Quote) On the "register" screen, when you click the "register" button, nothing happens. I didn't know it was necessary to provide UserCreated action. It wasn't in the code example that I got from the flutterfire web page (404 now https://github.com/firebase/flutterfire/tree/master/packages/flutterfire_ui) and it's not documented anywhere. It works fine with that included. (Quote) Make sure you pass a correct ActionCodeSettings and configure your app according to this documentation I didn't know it was necessary to pass ActionCodeSettings. It wasn't in the code example that I got from the flutterfire web page (404 now https://github.com/firebase/flutterfire/tree/master/packages/flutterfire_ui) and it's not documented anywhere. Email verify works ok for web. I guess it will work for android once I figure out how to use ActionCodeSettings. (Quote) Enable more sign-in methods problem. Please provide a reproducible example. #39 The system doesn't let me re-open closed issues. Regarding email verify, it would be preferable if the email address could be verified before a new user was registered in firebase. The original example code I got from flutterfire went straight from signup to profile screen but I found a new example that blocked getting to the profile screen until email was verified. It seems that the email verify options on the profile page are kind of redundant (and a bit clunky) when there is a nice "email verify" screen (that I didn't know about). It would be nice to have a public roadmap for when ui_auth will be useable in a production app. |
The person who wrote this had very good points, it may make sense to update the documentation. My experience was the exact same as his. |
Also had a similar experience I moved from the flutterfire package and it was not obvious how to get things working. Email Verification looks like it should just work looking at the code, the need for actionCodeSettings makes what is a simple process much more complex. |
Closing, as issues mentioned here were filed individually. Feel free to submit new issues if something is not covered |
Bug report
Using pub dev firebase_ui_auth 1.1.9
Flutter doctor
Run
flutter doctor
and paste the output below:Click To Expand
Flutter dependencies
Click To Expand
The text was updated successfully, but these errors were encountered: