firebaseui-web: google api iframe error

steps to reproduce this

OSX 10.11.6 , chrome Version 55.0.2883.95 (64-bit)
incognito
https://fir-ui-demo-84a6c.firebaseapp.com/ Try several times, if this error is not coming up.

There are two issues in the screenshot below. I am not sure the first one causes other issues, but following errors occur randomly when the first one is present.

Uncaught TypeError: r[t] is not a function
    at Object.Y.x.(anonymous function) [as loaded_0] (https://apis.google.com/js/api.js?onload=__iframefcb799082:10:484)
    at https://apis.google.com/_/scs/apps-static/_/js/k=oz.gapi.en._gEgtcvh1fE.O/m…d=1/ed=1/am=AQ/rs=AGLTcCNp1OHO8NH9OIu_qsqhhE2s-Jq6qA/cb=gapi.loaded_0:1:15
Y.x.(anonymous function) @ api.js?onload=__iframefcb799082:10
(anonymous) @ cb=gapi.loaded_0:1
iframe.js:118 XHR finished loading: GET "https://www.googleapis.com/identitytoolkit/v3/relyingparty/getProjectConfig?key=AIzaSyBgcSHxbo93P-N9Sh-ZIqgzvwicHDk_Skc&cb=1485132920219".
H.send @ iframe.js:118
Q.hj @ iframe.js:172
zh @ iframe.js:171
(anonymous) @ iframe.js:176
E @ iframe.js:85
Ch @ iframe.js:176
(anonymous) @ iframe.js:184
e.Wb @ iframe.js:89
Ce @ iframe.js:93
ye @ iframe.js:93
E.Oh @ iframe.js:92
ge @ iframe.js:85
firebase.js:180 Uncaught Error: Network Error
    at ontimeout (firebase.js:180)
    at api.js?onload=__iframefcb799082:10
ontimeout @ firebase.js:180
(anonymous) @ api.js?onload=__iframefcb799082:10
firebase.js:81 Uncaught Q {code: "auth/network-request-failed", message: "A network error (such as timeout, interrupted connection or unreachable host) has occurred."}
(anonymous) @ firebase.js:81

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 32 (12 by maintainers)

Most upvoted comments

I accidentally was able to consistently (well enough to find the pattern) replicate this on my workstation when I emulate an iPhone in Chrome developer tools. FirebaseUI internally creates a copy of the original Auth instance so that Auth state changes are not triggered prematurely on the original instance before the sign in process is completed. The problem is both instances (issue is in the core firebase-auth.js sdk) were late loading gapi external library and in the process a race condition was encountered, we are changing the logic so multiple instances share the same late loading mechanism and do not clobber each other. I think this seems to be the mostly likely reason for this issue. It should be fixed and released next week. I will ping this thread when it’s ready.

I apologize for the frustration in this issue. It is genuinely hard to fix a bug when we cannot replicate it.

bojeil-google on May 8, 2017

I can replicate this error too (on both low speed and high speed internet).

calclavia on Feb 17, 2017