Firebaseui-web: Help understanding "Missing Sender" when trying to send password reset email
[ Warning : Designer trying to code]
When I try to send a password reset email, I see the "missing sender" alert in my window and the "auth/invalid-email" error in my console to go along with it. I suspect that this has something to do with my email configuration. I did my darnedest to customize my email domain. I followed the steps in the firebase console, and my email client was verified.
As background, my problems first arose when I simply tried to click the 'send password reset' button from the firebase console, under the contextual menu for each user. This seems to be as far as I've made it, attempting to send the email programmatically. Any clues/hints/guesses offered would be greatly appreciated.
I apologize for the poorly formatted code, below, I'm not sure how to add returns and tabs.
function sendPasswordReset() {
var email = document.getElementById('email').value;
// [START sendpasswordemail]
firebase.auth().sendPasswordResetEmail(email).then(function() {
// Password Reset Email Sent!
// [START_EXCLUDE]
alert('Password Reset Email Sent!');
// [END_EXCLUDE]
}).catch(function(error) {
// Handle Errors here.
var errorCode = error.code;
var errorMessage = error.message;
// [START_EXCLUDE]
if (errorCode == 'auth/invalid-email') {
alert(errorMessage);
} else if (errorCode == 'auth/user-not-found') {
alert(errorMessage);
}
console.log(error);
// [END_EXCLUDE]
});
// [END sendpasswordemail];
}
itispeach
All 17 comments
Hi @itispeach, it doesn't seem that you are using FirebaseUI. For questions related to Firebase SDK, please use StackOverflow tagging firebase-authentication. More people will be able to help you there.
It seems that it may be a configuration related issue, so when you move your question to StackOverflow, please also explain how you customize your email domain, it may help.
BTW, to do block code spanning several lines, you should put 3 backticks (```) before and after your code snippet ;). I think GitHub also provide a UI button to create them.
TMSCH
on 29 Nov 2016
@TMSCH Salut Thomas! (francophone ici). Thanks for your response. I didn't actually mean to use the SDK — I was hoping to use the Firebase UI. I just realized I was hiding the "having trouble" button in my implementation. Now that's showing again, here's what happens when I try to use it, and this is why I hid it from my users. As you can see in the screenshot below, I'm getting "Error code: auth/internal-error." Not sure, but since I added a custom domain for sending emails, do I need to update the Action URL? If so, to what? The hint in the firebase console reads "Action URL should link to an interface for users to complete tasks (sign up confirmation, password resets, email address changes)." As of right now, I simply dropped the code for firebaseUI into my web page. Will firebaseUI give me "an interface for users to complete tasks?" Any point in the right direction would be greatly appreciated.
itispeach
on 30 Nov 2016
Salut! :) You shouldn't have to change the Action URL. The default points to a widget hosted by Firebase that includes all the handlers required. It is the recommended option.
Could you post the Network logs (there's a Network tab in the dev console), especially the one network request that fails? (I assume there should be one).
TMSCH
on 30 Nov 2016
Thank you for your time, Thomas. Here's a screenshot of what the network tab looks like :
I drilled down to more information. It only made sense to take a screenshot of the "Timing" section under And here's a look, drilling down :
Maybe there's an easier / prettier way to get this information to you, but I opted for copy & paste. You'll notice I left out the details under the "Header" sub-section of the Network tab. Because I'm generally clueless, I decided I would leave it out, until you ask for them/reassure me that it's okay to share those details in this venue. Below, you'll see the details of the Preview and Responses sub-tabs, pasted below :
Thank you. — Matthew
[PREVIEW]
————————
{,…}
error
:
{errors: [{domain: "global", reason: "invalid", message: "INVALID_EMAIL : Missing sender"}], code: 400,…}
code
:
400
errors
:
[{domain: "global", reason: "invalid", message: "INVALID_EMAIL : Missing sender"}]
0
:
{domain: "global", reason: "invalid", message: "INVALID_EMAIL : Missing sender"}
domain
:
"global"
message
:
"INVALID_EMAIL : Missing sender"
reason
:
"invalid"
message
:
"INVALID_EMAIL : Missing sender"
[RESONSES]
————————
{
"error": {
"errors": [
{
"domain": "global",
"reason": "invalid",
"message": "INVALID_EMAIL : Missing sender"
}
],
"code": 400,
"message": "INVALID_EMAIL : Missing sender"
}
}
itispeach
on 3 Dec 2016
Also, I haven't brought this to your attention, but my website is a squarespace site. I'm dropping the code in approved spaces where they allow it, but I wonder if it's making things harder.
This is where I drop the code for the widget, and that's all there is :
The rest of the code I am putting in their "inject in header" section (here's a peek with sensitive things masked out) If it is helpful to view all of the my code, I will paste it below. Thanks, Matthew.
itispeach
on 3 Dec 2016
As a small update : I decided to use javascript to create the 'firebaseui-auth-container' div and append it to the body of my page. This way all of my code was in the same spot in squarespace (and hopefully being embedded in the page together at the same time. Even in this scenario I am getting the same problem.
itispeach
on 4 Dec 2016
Hey itispeach,
Before I escalate this issue, can you check your email templates in the Firebase Console and double check you didn't modify or remove the sender email from your email templates? You could have also provided an invalid email with an invalid domain the process which is causing this problem.
bojeil-google
on 5 Dec 2016
Fair question! It is definitely there and it was also verified. As background, the mail client is Keiros (some implementation of a Microsoft Exchange server for the client I’m working with).
Matthew
On Dec 4, 2016, at 22:15, bojeil-google <[email protected] notifications@github.com> wrote:
Hey itispeach,
Before I escalate this issue, can you check your email templates in the Firebase Console and double check you didn't modify or remove the sender email from your email templates? You could have also provided an invalid email with an invalid domain the process which is causing this problem.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/firebase/firebaseui-web/issues/80#issuecomment-264769839, or mute the thread https://github.com/notifications/unsubscribe-auth/AQgMxTyLj7QEZea-CKtXJ-eX1L9IqJOVks5rE53fgaJpZM4K_Ggi.
itispeach
on 6 Dec 2016
Hi Matthew, can you try sending email in the Firebase console and see if it works? The cause of this error message is that there is some invalid value in the sender address/domain in the Firebase console.
wuyanna
on 7 Dec 2016
Hi Yanna, sending the email in the firebase console does not work. It never has in fact — even before I customized the domain. When I did customize the domain, I update my DNS records and received verification that it worked. Anyway, here's the error growl that comes in when I hit "Reset Password" from the contextual menu.
I returned the email template's domain to the default domain of my firebase app. I then tried it again and got the same error growl in the top right of the screen.
Do I need to return to the default URL? I changed my Action URL and can't remember what the default was. Could that be the problem?
itispeach
on 7 Dec 2016
It shouldn't have anything to do with Action URL. Can you check that the local part of the email sender (the part before @doamin) only contains alphabetic and numeric characters? Or change it to 'noreply' and see if that works? If that still doesn't work, let us know the project id and we can check for you
wuyanna
on 7 Dec 2016
Checked and tried. I'm still getting the same error. To confirm : I am now using {'noreply@{thedefaultfirebasedomain.com}. I'll send you the project ID directly.
itispeach
on 7 Dec 2016
@wuyanna How do I message you directly with the Project ID — is this something I need to keep sensitive and out of this thread?
itispeach
on 7 Dec 2016
Hi Matthew, so the issue is that there is an invalid character comma (,) in the Sender name. Since the sender name is also a part of the sender address, it needs to follow the email address standard, and I think comma is a reserved token. After I removed the the comma in Sender name, it seems the issue doesn't appear anymore.
wuyanna
on 7 Dec 2016
Woohoo! You rock! This has been killing me!
It just worked for me as well. I can’t thank you enough for figuring that out.
I’ll re-update my DNS records and see if my custom domain doesn’t work as well, as long as I keep the sender name the same. Sincerely, thank you for taking the time to help me,
Matthew
On Dec 7, 2016, at 3:27 PM, Yanna Wu notifications@github.com wrote:
Hi Matthew, so the issue is that there is an invalid character comma (,) in the Sender name. Since the sender name is also a part of the sender address, it needs to follow the email address standard, and I think comma is a reserved token. After I removed the the comma in Sender name, it seems the issue doesn't appear anymore.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/firebase/firebaseui-web/issues/80#issuecomment-265593585, or mute the thread https://github.com/notifications/unsubscribe-auth/AQgMxdpxSTgOt1eRs3ZqiMiPs_gb9xLDks5rFzLPgaJpZM4K_Ggi.
itispeach
on 7 Dec 2016
My pleasure. Thanks for using Firebase :)
wuyanna
on 7 Dec 2016
Exactly the same thing had been driving me crazy. Thank you for having this issue before me :)
Viral-Inc
on 6 Apr 2017
Related issues
deepfriedbrain
·
5Comments
mattpalermo
·
3Comments
smashah
·
5Comments
AnthonyNahas
·
3Comments
polo13999
·
3Comments
Most helpful comment
Hi Matthew, so the issue is that there is an invalid character comma (,) in the Sender name. Since the sender name is also a part of the sender address, it needs to follow the email address standard, and I think comma is a reserved token. After I removed the the comma in Sender name, it seems the issue doesn't appear anymore.