I’m currently facing an issue with Bubble’s official Google plugin while integrating it into my platform, and I would appreciate someone’s assistance in resolving it.
When a user signs up using the plugin, everything works fine initially. However, if the user logs out and then signs-up in using the same account, the data I previously stored for that user gets renewed or overwritten. That is due to the fact that I am doing some processing for new users when they sign up for the first time.
I want the system to recognize when a user has already signed up so that they aren’t re-signed up upon login, preserving the previously stored data.
Additionally, I have separate buttons for Signup and Login on my platform, but both are behaving similarly, taking the user to the permission/allow page and completing the signup process. My aim is to differentiate the two processes:
Signup should occur only for new users. Login should automatically log in existing users without triggering the signup flow.
Could someone guide me on how I can properly differentiate these two actions? Specifically, how can I ensure that the plugin recognizes returning users who’ve already signed up, bypassing the signup process and taking them directly to the login? And how can I redirect users who aren’t registered to the signup page instead?
You should just set a conditionnal on your workflow with a field that say “initial setup completed” is not yes. On your action to update the user on signup, set this field to yes.
Also @Jici Could you please tell me how to avoid the “Choose an Account” and then “Allow Permissions” pages for a user who has already signed up and is logging in the next time?
Will these pages always come irrespective of signup or login?
