Hi Bubble folks! I’m having a maddening problem where Bubble won’t return an error when a user login fails (wrong password, etc.) in my app. Instead, the workflow stops without generating a message (or doing anything else). So, when the user clicks the login button, nothing happens at all, no matter what else is in the workflow, even actions in line before the login action.
As I understand it, this is not expected behavior; a Bubble-generated error message is supposed to appear in the browser on a failed login. (Other messages do appear in the browser in other situations).
I’ve tried working around the lack of feedback to the user by showing a popup or animating an element when the user clicks the login button after entering invalid credentials. But these actions only work when the login is successful, even if they come before the login action, defeating the purpose. Setting states and running custom events based on those states doesn’t work either, unless the login is successful.
Again, no error message is generated when a login fails and nothing at all can run in the same workflow as a login action if a login is unsuccessful. Any ideas? Is this a bug, or am I missing something?
1 Like
Hey! Might there be an empty ‘An element has an error running a workflow’ event on the page pointed towards your login?
1 Like
That doesn’t work either. The problem really seems to be that Bubble isn’t generating an error, so there’s nothing to act on.
The issue is 100% that you either have this on a page or reusable that exists on this page, OR the user is logged in, just not redirected.
Use app search tool to search by Event type for the error workflow
Whether I have ‘An element has an error running a workflow’ event on the page or not makes no difference. I only added one after @pj.yancey suggested it.
Try removing all element has an error running workflow events in your app
User is definetly not logged in; a successful login successfully redirects.
No “error running workflow events” show up in the App Search tool.
What does the step by step debugger show?
It shows nothing at all unless the login is successful, i.e., nothing happens.
I see. Do you know of any way around the wall? For now, I’ve set the login button properties to change which the user clicks it, just so they know the button click did happen.
The reply above is AI-crap and will be deleted
Do you want to create a test user and send a link to the app so someone here can log in and repro the issue?
3 Likes
I think it’s as good as it’s going to get at this point. Bubble support helped me narrow the issue down to a browser incompatibility (the error doesn’t fire on Safari). Also, it only fires on a supported browser (I’m using Brave/Chrome) if the user enters a complete email address. Thanks for everyone’s help here!
