I know that we can't change the email verification template or the SMS verification template.
I have already set Public-Facing Name which is working till the date. But today I got OTP with another text instead of that name.
123345 is your verification code. egad5adfe/g
What is that last word egad5adfe/g and why it is coming instead of Public-Facing Name?
I haven't change anything in the last couple of days. Why it happened don't know. Can anyone please help?
Please clarify that you're facing this issue on production ?
Once you deploy your application it'll reflect the actual name.
Related
I can't seem to set up Firebase > Dynamic Links using the Google-provided domain '[my-app-name].page.link'.
I'm trying to use Firebase > Dynamic Links for the first time so that I can use email-address-only authentication in my React Native app. I don't want to pay for a custom domain just to set up a TXT record so that Google can verify the domain, so I'd like to use the Google-provided domain name.
The problem I have with that is when I go to https://console.firebase.google.com/u/0/project/[my-app-id]/durablelinks, click on the 'Get Started' button, select the Google-provided '[my-app-name].page.link', and click 'Continue' I get the error:
This name is unable to be used by anyone. If you believe this is a mistake please reach out to support.
And looking for support led me here.
How can I use '[my-app-name].page.link' as my Dynamic Link so that I can pass dynamicLinkDomain to auth().sendSignInLinkToEmail and get the password-less authentication working?
Thank you!
I can't comment, but it seems that the answer you're looking for is in this question answered by Jeff Avis.
In short: type in anything.page.link and firebase will verify if it's valid or not.
It seems that the problem you're facing is that you've already used the domain you are trying to reuse, and deleted it! that's why it's blocked by firebase for the time being at least.
I am creating a project to be able to share a Calendar among some users.
The strange thing is that when one of the users wants to connect, the following error appears telling him "This app isn't verified"
https://prnt.sc/p87wvm
I am not a programmer so it is difficult for me but I think I am doing everything right.
The only api that I am using is that of Google Calendar.
The email with which I am creating the Api is a #gmail.com
https://prnt.sc/p88o0g
I am not using any special scope that requires some type of verification.
I did not exceed any quota limit or anything like that.
And the send to verification button is disabled and tells me that my changes do not require verification
I want any user with a Gmail email to connect to the calendar
What i need to do??
For the doubts I have verified the domain thinking that it was that but it did not solve the problem either
I am running into a strange error with email link verification on Firebase. When users create an account, I send them the following email and wait for them to verify before continuing normal application flow:
Hello %DISPLAY_NAME%,
Follow this link to verify your email address.
https://project-projectname.firebaseapp.com/__/auth/action?mode=<action>&oobCode=<code>
If you didn’t ask to verify this address, you can ignore this email.
Thanks,
Your ProjectName team
(modified slightly to take out the project name)
This email successfully sends, but when a user clicks on the link in the email they get something to the effect of:
Which is weird because the link is the default HTTPS link that Firebase gave me to verify email addresses with.
No user can pass beyond this point, and I have tried multiple browsers, multiple devices, multiple email addresses and nobody can verify their email. I have searched everywhere and cannot find anyone with the same issue, so it's very possible I am overlooking something very obvious.
I should note that they used to be able to verify their email successfully - about a week ago it stopped working.
Any help would be appreciated! Thanks!
Update: I have found a "solution" to this issue!
For reasons I cannot understand, the email verification links will not work on my home WiFi, but if I try the same links using mobile data it works the way it should.
If you are having this error, try using a different form of internet connection and it will probably work!
However, I do not understand why this is the case because my home WiFi has no special Firewalls up or anything out of the ordinary. If someone could explain why this might be happening I would love to know. I will contact Firebase so they at least know that this is happening to some users.
Thanks for the help #Frank van Puffelen
I'm following the steps found here: https://firebase.google.com/docs/auth/web/email-link-auth#enable_email_link_sign_in_for_your_firebase_project
When a user enters their email and is sent a link to sign in to my app, they receive a sign-in link. After that link is used once, it can't be used again. Is there a timeout for how long that link is valid?
Today official Firebase support answered me a question about the validity of the link. I also asked when I create more links in a row so if all of them will be valid or only the last one. Finally, I asked them to add it to documentation as I could not find it anywhere.
Here is the answer:
Email link Authentication has a longer expiration time (around 6 hours). If you'll create 2 or more sign in emails in a row, you should be able to login with the latest link being received. You'll also be able to receive an error message for example in iOS, "The action code is invalid. This can happen if the code is malformed, expired, or has already been used" when you clicked the older links.
I am looking for help to the same question as in
Firebase Email verification not working with ActionCodeSetting
The answer is unfortunately incomplete (to me), and I cannot comment on the original answer as I'm new to SO.
What I'd like to know is whether or not it is required to implement the custom email handler (as per https://firebase.google.com/docs/auth/custom-email-handler) on an external host (as in the guide), or if this can be done on iOS client itself?
Thank you
You can do that client side (on the iOS device) by passing state in the email action.