-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Blank page renders with AngularFire 5.4.x #2314
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
We did a lot of Zone.js work that landed in 5.4, that could be causing trouble. Hmmmm... |
I'd say stick with 5.3.1 for now. Are you planning on migrating to ng 9 once it's out? Curious if you'd run into this with AngularFire v6 too, as in theory I rebased all that in... If you have an easy repro feel free to share, [email protected] |
Might related to #2309 |
Agreed. I'm taking the problematic share out and running the tests now. |
@anisabboud can you check |
(Yes, I'm planning to upgrade to Angular 9 and AngularFire v6 once it's out.) |
Excellent. Don’t hesitate to reach out if you have any trouble with the RC. |
what is the latest stable version of firebase and angular that work well with 5.4.2?
|
AngularFire 5.4 should work correctly with Angular 8 and any recent Firebase JS SDK version. See peerDependencies in published package.json |
latest stable version with angular 8 but with 9, is any already available? |
5.3.1
works fine for me with latest Angular 8.3.24 and Firebase 7.8.0.5.4.0
or5.4.1
, my angular app loads a blank page. There are no errors in the terminal/console (and logging auth state and user id is successful), but inspecting the page shows that the<app-root>
element contains only an empty<router-outlet>
and no other components were loaded...5.3.1
works fine again...Are there any breaking changes in
5.4.0
I should look for? Thanks!The text was updated successfully, but these errors were encountered: