I am using the Google and Facebook signup flows. When a user signs up with facebook, but then clicks on google in another session (when the user is logged out) I want to display a message saying this user has already signed up with facebook and re-direct them to the facebook login.
The error message is not displayed as a core message in bubble and instead just logs to the console, so I can’t use the unhandled error workflow in bubble to do this. I have attached a screenshot.
When you do a social media login, it’s actually like adding an integration or an authentication method to the user
And it looks at the uniqueness based on the authentication method level
e.g.
If a user has a Google account and tries to login with the same email to a -Facebook account it will create a new user
Another part is since this is like adding integration to the user, once the user is authenticated and logged-in, if he uses a workflow that triggers login with a new provider … the user then will be able to login using this method as well … even if it’s a different email
e.g.
after the user is authenticated, if the user triggered login or signup with Facebook, bubble will add another authentication method using Facebook [email protected] the user then will have 2 ways to access the same account
If another user tries to login with [email protected] using Google, it will login normally and the same if someone tried to use [email protected] using Facebook
What you can do in this case is to validate if the email exists in your database or not before creating a new user
This works! it does mean exposes the user email to everyone in the privacy settings though. Is there a way you can still maintain user email privacy and still achieve this?
Well, I’m glad you asked
Do it as a backend workflow that ignores privacy rules just to check for this and return yes/no or static text instead of the email
