-
Notifications
You must be signed in to change notification settings - Fork 255
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
uiconfig.callbacks are not called for email link sign in method if onAuthStateChanged listener is registered #91
Comments
The same happen to my example where I try to set up the Twitter provider, the Next.js examples - with-firebase-authentication |
Same here. Call back is not triggered for EMAIL_LINK_SIGN_IN_METHOD. |
I just ran into this same issue, the email link sign-in method does not trigger Does anybody know if this is a bug in firebaseui-web-react, or is it an underlying issue in firebaseui-web? |
Been having the same issue, except the callback isnt triggered when certain microsoft accounts log in |
Does anyone found a solution for this? |
up! same issue for GitHub provider |
I am using provider: EmailAuthProvider.PROVIDER_ID with EmailAuthProvider.EMAIL_LINK_SIGN_IN_METHOD and flow = redirect. I register a listener for onAuthStateChanged in componentDidMount and I have
(other parts of config skipped for brevity)
The onAuthStateChanged listener will be called but the signInSuccessWithAuthResult callback will not. If I get rid of the listener, the callback is hit. This issue only applies to email link sign in- google, facebook, etc[ work fine and call both the listener and the callback.
I need the signInSuccessWithAuthResult callback to take actions that need to happen only once on signup, rather than every time the user logs in/refreshes the page, which is what onAuthStateChanged would get me.
@jhuleatt @wti806 This seems like it might be related to these other issues issues: #67 or firebase/firebaseui-web#656 any thoughts?
@dankawka maybe related to the issue you called in #67 ?
The text was updated successfully, but these errors were encountered: