We cannot link your account to this email because there is already an account for this email

Need help APIs
22

I am having this same problem (again). And for me it is not how you have described @deadpoetnsp. Yesterday my Google had been working (and for the last two weeks) and now it is not. I have logged in the same way with these same email address and now it throwing the error “We cannot link your account to this email because there is already an account for this email”

Any Ideas?

3 Likes
23

@deadpoetnsp, thanks for the summary of the situation. Do you know what steps a person can then take to disassociate an account from a Bubble user after it has been linked via oAuth?

@eve, any thoughts from a Bubble perspective on this?

24

Hey there @eLPDev,

To disconnect your google account or such from a Bubble user you simply just need to send a password reset to that user, then they should be good to login with a password rather than with google or another provider.

25

@johnny, thanks for the reply. The problem here is that this happens every time I attempt to use the sign up/login option, which I’d think shouldn’t be happening since this should log the user in successfully after the first attempt.

1 Like
26

This is a common issue and a reason I made my own google oauth api calls. It’s like sometimes the system doesn’t recognize that the user already exists. It’s as if A token has expired or been revoked but that’s not the case either. I’m not sure what it is but there’s definitely an issue using this feature.

27

I am experiencing this issue as well…has it been solved?

28

What I’ve noticed is the fix for this is to make sure that if a user created their account manually using the bubble db that they need to do oauth when signed into the email already taken if that makes sense

29

Thanks. This is my current setup too. The strange part is even if one of my accounts use oauth directly (didn’t use traditional bubble db to register), the problem still happen from time to time…it could be working last minute but not this time

30

This is actually not a bug. Google keeps the session open and you probably don’t have a -user profile group- showing the user on your index page (because after signing in it goes to dashboard or similar, right?).

So add to you index page a group where shows the user if it’s logged in, you can add a logout button as well.

2 Likes
31

This was never resolved, right? I’ve only ever had google oauth for sign ups on my app, and I get this error constantly.

3 Likes
32

Hello everyone,

I’m strugglin with the same problem here, with spotify api.
The problem appears when two users try to connect on the same browser (one after the other, not same time obvisouly)
So, when a user has been connected once et linked his spotify account, nobody can use the app after him…
It works when I clear cookies, or when I navigate in private mode, but it’s not a solution…

I don’t understand how and why the session is not link to the user but to the browser ?

Please can someone help me ?

1 Like