using cloud functions to update emailVerified is not logical

[yk-eta]

trafficstars

Problem

I am working with social account linking on existing email password account, when user binding with facebook is fine, but when user binding when google, the original email password account is gone.

I had read though some of those report, that using cloud functions to update emailVerified for created user to true, but it is not for my scenario as it is existing user and I had to move my plan to Blaze plan in order to use cloud functions.

https://github.com/firebase/firebase-js-sdk/issues/340

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[daveteu]

You don't get charged immediately with Blaze plans, since you still enjoy all the resource from free tier first before u get charged.

[yk-eta]

not only the fees, even with setting emailVerified to true with cloud functions, the login logic for google provider is still making different comparing with other provider, should it be an option and default behavior for project instead of force implementation? as it can causing alot of issue like affecting user experience.

[DellaBitta]

Hi @yk-eta,

Since this deals with backend behavior at the account level (and I believe not the SDK) I recommend opening a ticket with Firebase support. I hope this helps!

[google-oss-bot]

Hey @yk-eta. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

[google-oss-bot]

Since there haven't been any recent updates here, I am going to close this issue.

@yk-eta if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.