function set up correctly, checked firestore logs, not error occurs, just cant received any email from firestore. My current SMTP is using gmail, not sure what cause the problems.
some error showing in Collection: Error: Missing credentials for "PLAIN"
Related
When my app calls linkWithCredential Firebase sends an email titled "Your sign-in email was changed" automatically.
This happens when an user enters the email address different from the current one.
Is there any way to prevent Firebase from sending such email?
I'm trying with firebase v9.10.0 npm package.
The message is sent to the user's current email address to alert them to the change of their sign-in method/credentials. There is no way to control whether Firebase sends this email on calling the linkWithCredential API.
I recommend looking at the flow of your code, as wanting to suppress this message typically means that you're doing something unexpected. For example, if you know the user's current email address, it's probably better to detect when they enter a different value before calling the Firebase API, and ask them to confirm the value.
I'm developing a firebase web project where user can sign up and login via email / password.
Right now, when I send a verification email (firebase.auth().currentUser.sendEmailVerification()).
When I receive the email (few seconds later) and follow the link, I just get this error:
However, my email is still not verified - and there are no further error messages. How can I complete the email verification?
Retrying the procedure gives me a different link each time, but with the same result.
Im trying to link accounts credentials using firebase_auth, google_sing_in and facebook_login packages, but i dont know how to handle this error, the fetchSignInMethodsForEmail requires an email and the error callback doesnt return any. Please help
This is the error:
PlatformException(ERROR_ACCOUNT_EXISTS_WITH_DIFFERENT_CREDENTIAL, An account already exists with the same email address but different sign-in credentials. Sign in using a provider associated with this email address., null)
This is the documentation in the source code:
ERROR_ACCOUNT_EXISTS_WITH_DIFFERENT_CREDENTIAL - If there already
exists an account with the email address asserted by Google. Resolve
this case by calling [fetchSignInMethodsForEmail] and then asking the
user to sign in using one of them.
I successfully auth with phone-number. (I can check firebase.auth.currentUser that I'm logged in.)
Then I'm calling my firebase admin route which have admin.auth().updateUser(uid, somevalues) to set user displayName and email.
After this step finished and my user data changed displayName and email.(It is checked in firebase console)
In my auth I run firebase.auth().currentUser.reload() to get updated user data and suddenly there is error auth/user-token-expired
I have checked only after I use admin.auth().updateUser(....) my token is lost. If I do not run this command then I can do firebase.auth().currentUser.reload() without problem.
UPDATE: Only if I set email when calling admin.auth().updateUser(....) my token inside app becomes invalid. If I change only displayName token remains valid.
I'm not sure what the exact question is here, but reload() will use a refresh token, however, refresh tokens expire when "A major account change is detected for the user. This includes events like password or email address updates."
See: https://firebase.google.com/docs/auth/admin/manage-sessions
So when your refresh token expires (due to the 'major account change'), you need to re-authorize..
I'm getting the token from the firebase using the client end and passing it to the server/backend for storage, but when I call subscribe to topic using that firebase token on the server, I'm getting
{"error":"No information found about this instance id."}.
This happens almost all the time, but sometimes it works, I don't seem to understand what is happening here?
I started receiving this message in a response with 404 as the status code when the client unregistered from push notifications on the client side (when he/she did logout, for example, I unregister the user from receiving push notifications in the app). The next time the client logged in, he/she received a new registration token.
I don't know if and when your app unregisters from push notifications, and if this is the only case in which such response errors happen, but that was the reason in my case, and it could be yours too.
When I try to subscribe/unsubscribe from topics and receive 404 when accessing https://iid.googleapis.com/iid/[...], I simply invalidate the respective registration id in my codebase so as to ignore it (and stop trying to subscribe or unsubscribe again).
In the documentation, in the final section that is about Error Responses, it says:
HTTP status 404 (Not found) - Invalid HTTP path or IID token not
found. Check error messages for detailed information.
I'm pretty much sure that the url must be valid, otherwise it should give errors when testing, so I assume that the token (registration id) is invalid. I would prefer that the error returned a code such as InvalidRegistration (like the error codes that are returned when sending push notifications), but for now the error is a normal text message (for the 404 error), so I base myself only in the status.
I hope it helps.