Bubbles Google oAuth plugin shows a consent screen on every sign in

Need help Plugins
1

I am having an issue with the oAuth plugin by bubble that I have not had before. When users create an account with google, its shows a consent screen along the lines of:

"By continuing, Google will share your name, email address, language preference, and profile picture with xyz.com…’

This is normal and expected, however, when an existing user uses sign in with google to simply sign in to their account, they are prompted to re-consent. It is my understanding that this should not be happening for existing users. Any help appreciated.

Also worth noting, I have tried with a scopeless google project and an approved project with non-sensitive scopes.

1 Like
2

I noticed the same issue happening with my app. Only recently though

3

I’m also seeing this. The consent screen is very recent in the last week and has been hurting my signup conversions. Can someone please look into this?

4

I noticed bubble’s oAuth portion of their documentation is no longer available… Strange.

5

Looks like a known issue, Bubble needs to change some stuff on their end Google auth2 asks for permission every time when asking for access to the app - Stack Overflow

6

I’m curious what’s going on with this – even authenticating to Bubble itself via Google OAuth results in the consent dialog reappearing (I think Bubble uses its own Google OAuth plugin). Is there a way tag Bubble for a response or status update?

7

Mass Bug reports tends to get things fixed pretty quickly : ). I’ll submit one myself.

8

Any update on this ? Seems to happen consistently

1 Like
9

Also looking for an update on this. Annoying for users to have to provide consent every time they login with Google. @fede.bubble any movement on fixing this issue?

10

Any update on this?
At first I thought it was some issue at my end.

The login flow is a mess because of this.

11

Did anyone get an update on this?

12

Second that. Anyone?

13

Any updates ?

14

I have an active support ticket for this issue. No updates yet.

15

They responded with: use the CustomAPI method and don’t use the plugin. If you want this to stop behaving this way its a feature request.

16

From my testing today, the user is also shown the consent screen when logging in to an existing account when I implement oauth using the API connector and “Oauth2 user-agent flow”.

I am not sure what they mean by “use the customAPI method” - I am not using the plugin and this still happens…