Firebase Web SDK createUserWithEmailAndPassword not logging in users after creation











up vote
0
down vote

favorite












I'm using Firebase email/password authentication.
This provider is activated for this project in Firebase console.
I'm using the Web SDK, and it is properly configured.



I have a form to signup that prompts the user to enter an email and a password to signup and authenticate.



firebase.auth().createUserWithEmailAndPassword(this.email, this.password)



is called when the user is signing up. The user is then directed the next step to fill his/her profile.



At this point



fb.auth.onAuthStateChanged(fbUser => {
if (fbUser) {
console.log('Logged in. User is: ', fbUser)
} else {
console.error('not logged in')
}
})


returns 'not logged in' while the user should be logged in according to the Firebase documentation (https://firebase.google.com/docs/auth/web/password-auth)










share|improve this question






















  • Firebase version 5.5.8
    – Stephane Paquet
    Nov 12 at 3:35










  • Hmm... that sounds weird. Can you reproduce it in a site like jsbin or stackblitz, so I can have a look?
    – Frank van Puffelen
    Nov 12 at 4:17










  • The only way I can see this happening is if the "next step" is a separate page (so a reload). In that case onAuthState should fire twice: first with no user, and then later (once the user token is validated) with the actual user.
    – Frank van Puffelen
    Nov 12 at 4:18










  • It's not a reload. I'm using a stepper. So everything is happening on the same page.
    – Stephane Paquet
    Nov 12 at 5:56










  • Agree that this is weird as there is a call to sendEmailVerification() in the callback section of createUserWithEmailAndPassword which is working as newly created users are receiving the email to confirm their email address.
    – Stephane Paquet
    Nov 12 at 5:58















up vote
0
down vote

favorite












I'm using Firebase email/password authentication.
This provider is activated for this project in Firebase console.
I'm using the Web SDK, and it is properly configured.



I have a form to signup that prompts the user to enter an email and a password to signup and authenticate.



firebase.auth().createUserWithEmailAndPassword(this.email, this.password)



is called when the user is signing up. The user is then directed the next step to fill his/her profile.



At this point



fb.auth.onAuthStateChanged(fbUser => {
if (fbUser) {
console.log('Logged in. User is: ', fbUser)
} else {
console.error('not logged in')
}
})


returns 'not logged in' while the user should be logged in according to the Firebase documentation (https://firebase.google.com/docs/auth/web/password-auth)










share|improve this question






















  • Firebase version 5.5.8
    – Stephane Paquet
    Nov 12 at 3:35










  • Hmm... that sounds weird. Can you reproduce it in a site like jsbin or stackblitz, so I can have a look?
    – Frank van Puffelen
    Nov 12 at 4:17










  • The only way I can see this happening is if the "next step" is a separate page (so a reload). In that case onAuthState should fire twice: first with no user, and then later (once the user token is validated) with the actual user.
    – Frank van Puffelen
    Nov 12 at 4:18










  • It's not a reload. I'm using a stepper. So everything is happening on the same page.
    – Stephane Paquet
    Nov 12 at 5:56










  • Agree that this is weird as there is a call to sendEmailVerification() in the callback section of createUserWithEmailAndPassword which is working as newly created users are receiving the email to confirm their email address.
    – Stephane Paquet
    Nov 12 at 5:58













up vote
0
down vote

favorite









up vote
0
down vote

favorite











I'm using Firebase email/password authentication.
This provider is activated for this project in Firebase console.
I'm using the Web SDK, and it is properly configured.



I have a form to signup that prompts the user to enter an email and a password to signup and authenticate.



firebase.auth().createUserWithEmailAndPassword(this.email, this.password)



is called when the user is signing up. The user is then directed the next step to fill his/her profile.



At this point



fb.auth.onAuthStateChanged(fbUser => {
if (fbUser) {
console.log('Logged in. User is: ', fbUser)
} else {
console.error('not logged in')
}
})


returns 'not logged in' while the user should be logged in according to the Firebase documentation (https://firebase.google.com/docs/auth/web/password-auth)










share|improve this question













I'm using Firebase email/password authentication.
This provider is activated for this project in Firebase console.
I'm using the Web SDK, and it is properly configured.



I have a form to signup that prompts the user to enter an email and a password to signup and authenticate.



firebase.auth().createUserWithEmailAndPassword(this.email, this.password)



is called when the user is signing up. The user is then directed the next step to fill his/her profile.



At this point



fb.auth.onAuthStateChanged(fbUser => {
if (fbUser) {
console.log('Logged in. User is: ', fbUser)
} else {
console.error('not logged in')
}
})


returns 'not logged in' while the user should be logged in according to the Firebase documentation (https://firebase.google.com/docs/auth/web/password-auth)







firebase firebase-authentication






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 12 at 3:33









Stephane Paquet

1,6541423




1,6541423












  • Firebase version 5.5.8
    – Stephane Paquet
    Nov 12 at 3:35










  • Hmm... that sounds weird. Can you reproduce it in a site like jsbin or stackblitz, so I can have a look?
    – Frank van Puffelen
    Nov 12 at 4:17










  • The only way I can see this happening is if the "next step" is a separate page (so a reload). In that case onAuthState should fire twice: first with no user, and then later (once the user token is validated) with the actual user.
    – Frank van Puffelen
    Nov 12 at 4:18










  • It's not a reload. I'm using a stepper. So everything is happening on the same page.
    – Stephane Paquet
    Nov 12 at 5:56










  • Agree that this is weird as there is a call to sendEmailVerification() in the callback section of createUserWithEmailAndPassword which is working as newly created users are receiving the email to confirm their email address.
    – Stephane Paquet
    Nov 12 at 5:58


















  • Firebase version 5.5.8
    – Stephane Paquet
    Nov 12 at 3:35










  • Hmm... that sounds weird. Can you reproduce it in a site like jsbin or stackblitz, so I can have a look?
    – Frank van Puffelen
    Nov 12 at 4:17










  • The only way I can see this happening is if the "next step" is a separate page (so a reload). In that case onAuthState should fire twice: first with no user, and then later (once the user token is validated) with the actual user.
    – Frank van Puffelen
    Nov 12 at 4:18










  • It's not a reload. I'm using a stepper. So everything is happening on the same page.
    – Stephane Paquet
    Nov 12 at 5:56










  • Agree that this is weird as there is a call to sendEmailVerification() in the callback section of createUserWithEmailAndPassword which is working as newly created users are receiving the email to confirm their email address.
    – Stephane Paquet
    Nov 12 at 5:58
















Firebase version 5.5.8
– Stephane Paquet
Nov 12 at 3:35




Firebase version 5.5.8
– Stephane Paquet
Nov 12 at 3:35












Hmm... that sounds weird. Can you reproduce it in a site like jsbin or stackblitz, so I can have a look?
– Frank van Puffelen
Nov 12 at 4:17




Hmm... that sounds weird. Can you reproduce it in a site like jsbin or stackblitz, so I can have a look?
– Frank van Puffelen
Nov 12 at 4:17












The only way I can see this happening is if the "next step" is a separate page (so a reload). In that case onAuthState should fire twice: first with no user, and then later (once the user token is validated) with the actual user.
– Frank van Puffelen
Nov 12 at 4:18




The only way I can see this happening is if the "next step" is a separate page (so a reload). In that case onAuthState should fire twice: first with no user, and then later (once the user token is validated) with the actual user.
– Frank van Puffelen
Nov 12 at 4:18












It's not a reload. I'm using a stepper. So everything is happening on the same page.
– Stephane Paquet
Nov 12 at 5:56




It's not a reload. I'm using a stepper. So everything is happening on the same page.
– Stephane Paquet
Nov 12 at 5:56












Agree that this is weird as there is a call to sendEmailVerification() in the callback section of createUserWithEmailAndPassword which is working as newly created users are receiving the email to confirm their email address.
– Stephane Paquet
Nov 12 at 5:58




Agree that this is weird as there is a call to sendEmailVerification() in the callback section of createUserWithEmailAndPassword which is working as newly created users are receiving the email to confirm their email address.
– Stephane Paquet
Nov 12 at 5:58

















active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53255626%2ffirebase-web-sdk-createuserwithemailandpassword-not-logging-in-users-after-creat%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53255626%2ffirebase-web-sdk-createuserwithemailandpassword-not-logging-in-users-after-creat%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Guess what letter conforming each word

Port of Spain

Run scheduled task as local user group (not BUILTIN)