Repository navigation
AngularFire breaking change between 5.1.3 and 5.2.0 #2115
Description
Hello,
This is an issue regarding a breaking change going from AngularFire 5.1.3 to 5.2.0 that I'm unsure that it is the intention.
See the closed issue here: firebase/firebase-js-sdk#1837 ; closed because of a request to re-open here.
Could of course be that this is intended behaviour but I wouldn't think so.
Activity
N-Andronopoulos commentedon Jun 27, 2019
Same issue as me: #2124
LanderBeeuwsaert commentedon Jun 27, 2019
Glad I'm not alone haha
N-Andronopoulos commentedon Jun 27, 2019
Just turn off aot and you're good to go till its resolved.
angular.json
LanderBeeuwsaert commentedon Jun 27, 2019
ok cool. Yeah thanks, but that would affect our production environment too much then. So not an option for us.
matheo commentedon Jul 13, 2019
@jamesdaniels this issue got attention in the
firebase-js-sdkrepo, but here it remains without a solution :( I've spent most of my day today trying to figure out the build issue and I just got here...@LanderBeeuwsaert please rename this ticket to "Production Build Fail" or "Blank Screen of Death" so others can reach this easier, and figure that the only solution is to not optimize the bundle and get a ton of additional Mb in our bundle.
jburson commentedon Jul 15, 2019
@jamesdaniels Version 5.2 should be rolled back unless a fix is coming very soon. This AOT bug is catastrophic and makes this version useless.
matheo commentedon Jul 16, 2019
Refs #2117