-
Notifications
You must be signed in to change notification settings - Fork 4k
🐛 [firebase_ui_auth] Sign methods icons are blank in ProfileScreen
#10280
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
Comments
Hi @gaetschwartz, do you see any errors in your console? Does this reproduce with the example app? |
Edit: It seems to work on the example, even in 1.1.8, where it doesn't in my two apps. Any clues what it could be ? |
Can you share a complete minimal reproducible code sample so that we can investigate this? |
Alright, so in the example, it uses a custom font. flutterfire/packages/firebase_ui_auth/example/pubspec.yaml Lines 75 to 78 in cdaaff0
If it's commented out, the Google logo becomes empty. ![]() Is it a new requirement to specify the custom font ? Can't the package do it by itself ? Edit: I can confirm that when specifying the font, the icons work fine. |
ProfileScreen
ProfileScreen
Not that I'm aware of.
Ideally, this should be handled by the package unless there's something that I'm not aware of that will prevent it from handling it. Bug Info
If this is working as intended, we should at least document this. /cc @lesnitsky |
There is a note that mentions font requirement on migration guide, will also add to main docs. |
Bug report
Describe the bug
The icons of sign in methods are empy for some reason.
Steps to reproduce
This only happens since
1.1.8
.Expected behavior
Icons should have proper appreance, like hte email one.
Sample project
https://zapp.run/edit/firebase-ui-go-router-za5206vca530?entry=lib/main.dart&file=pubspec.yaml
Flutter doctor
Run
flutter doctor
and paste the output below:Click To Expand
Flutter dependencies
Run
flutter pub deps -- --style=compact
and paste the output below:Click To Expand
The text was updated successfully, but these errors were encountered: