How are you getting the Signup/login with a web browser to work? I’ve been having issues since the feature’s been released and kinda gave up, but just revisited and same issues occur still
Basically what’s happening is when I use the Signup/login with a web browser and select the same page as my sign in page, then on BubbleGo, I sign in as usual, after signing me in, it just brings me to the page it would if I was on the web app version and doesn’t bring me back into the app.
Is this a bug? Or am I maybe just doing something wrong?
For reference, the BubbleGo login uses signup/login with a web app so we know that it works, but we are definitely seeing users having trouble setting it up properly.
What does the logic look like on your web signup/login page?
I have a “User is logged in” workflow I think I saw that somewhere on the forum that worked but it’s not working for me. Is it the conditionals I have?
I had a similar issue last week. After the login on the Web Browser completes, the page was redirected to my list of Bubble Apps in BubbleGo rather than the App I was trying to login to.
However, today when trying to recreate this, I cannot start my app at all using BubbleGo on Android. Once I select the App I wish to open, I am now getting the Bubble blue background which never changes or returns to my list of Bubble Apps…
The Login redirect issue only happened when using the BubbleGo for Android. When Using the iOS version through the TestFlight tool, the Login via a Web browser worked correctly.
Yes, the docs show this as a bit of a black box at the moment:
Perhaps, some further notes on how to follow the User is Logged in sequence would help prevent incompatible approaches being used.
I assume there is some detection of “User is logged in” that prevents redirects, closes the web browser action and stores the User in the native app. Otherwise, our users would follow any Navigation on the web app and get stuck there. Perhaps your “User is logged in” condition is preventing the Native App’s version from running?
The final step in my login sequence uses a “Navigate to” rather than a “Do When” condition:
